Orbit

Add an approval step before an AI agent merges code

Chris Rupp

First, require approval in GitHub

You can gate agent merges without Orbit. Protect the branch that receives production work, keep agent work on a task branch, and require a human review plus meaningful CI checks before merging.

  1. Open the repository’s Settings, find Rulesets, and choose New ruleset → New branch ruleset. Name it and target your default branch, such as main. Set enforcement to Active when you are ready to enforce it. Follow GitHub’s current ruleset creation instructions.
  2. Select Require a pull request before merging, and configure the number of required approving reviews. Requiring a PR alone does not require approval. Choose a human reviewer for agent work. See GitHub’s pull request rule and review settings.
  3. Select Require status checks to pass before merging and add the actual CI checks that establish your acceptance criteria. See GitHub’s status-check rule.
  4. Decide how to handle changes after approval. GitHub documents options to dismiss stale approvals or require approval of the most recent reviewable push by someone other than the pusher. Choose the policy that ensures the final diff gets reviewed. See the review settings.
  5. Review the bypass list. Keep the agent’s identity and any role it uses out of it if you want the gate to bind that agent. Save the ruleset. GitHub describes bypass permissions and active enforcement.

If your repository uses classic branch protection, configure required PR reviews and status checks there instead. Review administrator bypass behavior too. Check feature availability for your repository and plan in GitHub’s protected-branch documentation.

Source check: the linked GitHub documentation was reviewed for this guide. Use those pages when configuring your repository; labels and plan availability can change.

Prove the gate works

Open a harmless test PR using the same identity the agent uses. Before anyone approves it, confirm the required review is still outstanding. Run the required CI checks and inspect the merge requirements. Then approve the final diff through the designated human account and confirm the requirements are satisfied. If you enabled stale-approval dismissal, add a harmless change and confirm another review is needed before proceeding.

Give the agent a concrete instruction: create a task branch, implement the request, run the documented checks, publish the commit and open a PR for review. Keep repository settings aligned with that workflow so the approval requirement survives a missed instruction.

Read the code and reproduce the requested behavior before approving. Check the commit, the diff and the tests for a manual verification checklist.

What Orbit adds before main: approval before work starts

Orbit adds a review point earlier in the workflow. In Approval & Review, each queued prompt waits for approval before it runs. That lets you review the intended scope, acceptance checks and instructions before an agent changes code. The GitHub merge gate above reviews the resulting change before it reaches main.

To use that earlier gate, follow Queue & Approve a Prompt: open Pipeline → New Prompt, choose the project, write the request and queue it. Read the prompt and the pre-check warning chips, then click Approve when the work is ready to run. Include the task-branch and PR-review requirement in the prompt if that is your repository’s publication workflow.

The Queue & Approval reference documents review configuration by complexity tier and an approval receipt for the exact queued work. Its amber pre-check chips call attention to risks such as install commands or wide scope; they inform your decision and do not block approval themselves. Prompt approval authorizes that work to start. Keep the repository’s required human PR review in place for the merge decision.

After completion, Orbit’s documented validation pass inspects the commit diff and surfaces outcomes such as Ghost Ship or Wrong Files. Use that signal alongside your own acceptance checks. For the separate Sweep correction workflow, the Convergence Gate ends on a pending human-merge card containing the accumulated diff and loop result.

A reviewable handoff

Before the human merge decision, ask for the original request, implementation commit, full diff, actual check results and any missing or unverified behavior. Review those against the final revision. A prompt approval, a clean automated label and a human approval of the final code each answer a different question.

Continue with verifying whether the agent actually finished, or see Orbit’s features.

Before approving work you will leave running unattended, use the overnight safety checklist to review sandboxing, permissions, spending limits and the morning handoff.