Start here · GitHub private preview
Decide if a Gated pilot fits your next branch request.
A practical path from a specific GitHub action to a reviewable evaluation. Check the scope, access terms and evidence before preparing a pilot.
Step 1
Check whether the preview fits your need
Start with one non-critical GitHub repository and a branch-creation request. If you need merges, force pushes, deletions, production deployments or automatic control of every agent tool, the current preview does not cover that need.
Step 2
Review the exact GitHub operation
The preview creates one uniquely named branch at an exact existing commit in a selected repository. Review the GitHub connection and credential boundary before choosing a target.
Step 3
Check the current access terms
Read the Founding offer, eligibility and terms before applying. Access is reviewed; joining the updates list does not accept an application or activate a workspace.
Step 4
Choose a target, reviewer and evidence
Record the repository, unique branch name and full existing commit SHA. Name an authorized reviewer and decide how you will compare the receipt with GitHub readback and evaluate revocation.
Keep a written evaluation record
Use the manual scorecard to record your target, approval review and evidence. It is a worksheet you complete yourself; downloading it does not run a check or configure Gated.
Download the pilot scorecardChoose your agent workflow
The Codex and Claude Code previews use a reviewed project skill to explicitly route the scoped request through the Gated CLI. Independent provider tools and credentials remain outside this path.
Review alternate credential paths