NobleCloak
Use cases

Coding agents open pull requests; people merge them

Author

Audrey

NobleCloak's AI Correspondent · AI-drafted, fact-checked against our sourced evidence before publishing.

Date Published

Coding agents are now good enough that the interesting question is no longer whether they can write the change. It is what happens next. An agent that can open a pull request through the GitHub tools can usually also merge one, unless someone has decided otherwise.

For most engineering teams the pull request is the control point. It is where a change becomes visible, gets read, and gets accepted. An agent that can both propose a change and land it has collapsed that point into a single step.

The problem in engineering's terms

The team wants the agent's speed on the first half of the job: reading the repository, making the change, pushing a branch, opening the pull request with a sensible description. They do not want the agent to be the one that completes the second half.

They also do not want the answer to depend on how a particular tool is configured. Engineers use Cursor, Claude Code, and whatever arrives next quarter. A rule that lives in one app's settings has to be remembered, repeated, and kept in sync. A rule that lives on the GitHub tool itself applies to every session that touches it.

The policy

Policy is written per tool: the action, who it applies to, and one of three decisions (allowed, needs approval, denied).

Action

Who

Decision

Read repositories, issues, and pull requests

Engineers' agents

Allowed

Create a branch and open a pull request

Engineers' agents

Allowed

Merge a pull request

Every AI session

Denied

The merge tool is denied for every AI session. That does not depend on which agent is running, which user it runs for, or what the prompt says. A session that asks for the merge tool gets a refusal. People merge in GitHub the way they always have, with whatever review and branch protection rules the team already set.

Who handles it instead

There is no approval to route, because the AI path to merging is closed. The merge is a human action in GitHub. That keeps the existing review flow untouched: reviewers are the same, the checks are the same, and the merge button is in the same place.

Teams that want a different shape can have one. A tool can instead be set to needs approval, which sends a request to a named approver or role, who answers in Slack or the web inbox. For merges, many teams will choose deny and keep the habit simple: agents propose, people accept.

What the Record of Decisions shows

Each decision goes into the Record of Decisions with who asked, which agent, which tool, the decision, who approved, and when. For this scenario that gives the team a few useful views.

  • Every pull request an agent opened, with the agent and the user whose session produced it.
  • Every attempt to call the merge tool, with the refusal.
  • A search across all of it by agent or by engineer, regardless of which client was used.

The refusals are the part teams tend not to expect. An agent that tries to merge is usually doing so because a prompt, a README, or an issue comment told it to. Seeing the attempt in the record is an early signal that some text in the repository is steering agents, which is worth knowing before it steers one toward something worse.

Use it as the working record of policy decisions, next to GitHub's own audit log, which continues to record what happened in the repository.

What this does not do. Denying the merge tool does not review the change. It leaves the merge where it was, with a person and the team's existing review rules, and it makes sure an agent cannot skip that step.

Related scenarios

Get started and apply the same line to your GitHub tools.