Skip to content
Gated

Developers

Start with one GitHub branch request.

Gated’s private preview governs explicitly routed branch creation at an exact existing commit in a selected non-critical repository. Independent provider credentials can bypass this path.

  1. 01

    Review the request

    Check the selected repository, new branch name and full existing commit SHA.

  2. 02

    Review the decision

    Policy returns Allow, Require approval or Deny with a reason. Approve with a passkey when required.

  3. 03

    Request execution

    Execution is a separate step through the scoped GitHub App path. Approval alone creates nothing.

  4. 04

    Verify the result

    Compare the execution record with independent GitHub branch and commit readback.

Illustrative review fields · not an API schema

One operation, three exact inputs.

Repository
example/pilot-repository
New branch
gated/pilot-review
Existing commit SHA
533262250d35b80d779dff1fea95273c808c389b

These are example values, with no live action or receipt. Use the full SHA of a commit that already exists in your selected repository. A change to the repository, branch or commit is a different request that needs its own review.

Use the branch review guide

Prepare the controlled path.

You need pilot access, a non-critical repository you administer, an approved GitHub connection, scoped agent authority and a human approver with a passkey. Creating a branch may trigger repository workflows.

Codex and Claude Code use explicit project skills and CLI routing in the preview. Their runtime rehearsals used safe mode; live GitHub execution was verified separately through the downloaded CLI. The skills do not automatically intercept other tools.

Read the full GitHub requirements →

Choose your next step.

Review pilot fit before checking access availability. Planning and joining updates do not grant immediate access.

Plan your first pilot Check whether the preview fits your workflowMap credentials outside the boundary

Read the permission model.

Read AI Agent Permissions vs API Keys, follow the public preview guide, or inspect the security boundaries. PR merge, force push, branch deletion and production deployment governance are outside the verified pilot scope.