Skip to content
Central Agentic Ops

Install and Run Safely

Use this guide to reach a safe first result: one installed bundle, one target repository, and one staged run that cannot write to GitHub. Keep the control-plane repository private throughout setup.

Before You Start

You need:

  • a private repository to host the control plane;
  • one low-risk target repository for validation;
  • permission to configure Actions variables and secrets in the control-plane repository;
  • a GitHub App or fine-grained PAT if the target is private or internal.

For public repositories, you can complete a bounded staged run with the built-in GITHUB_TOKEN. See Choose credentials before using private targets, a separate review repository, or live mode.

1. Choose Your Scope

Use an enterprise-operated repository in a designated organization when workflows must reach repositories across organizations. Use an organization-operated repository when all targets belong to one organization.

The control plane coordinates installed workflows; it does not replace GitHub rulesets, protected environments, Actions policies, or repository administration. Review scope and enforcement limits before broader adoption.

2. Install a Bundle

Install the full catalog or one bundle into the private control-plane repository. The installation provides:

  • an orchestrator that selects repositories and dispatches work;
  • focused worker workflows;
  • shared authentication and fail-closed policy;
  • independent rollout settings that default to staged.

After installation, confirm that the generated orchestrator and worker workflows are present and enabled. Pages reporting is optional and is not installed by default.

3. Configure the Minimum

  1. Add a GitHub App or PAT when the built-in token cannot access the target. Follow Choose credentials.
  2. Confirm the target owner is allowed by CENTRAL_AGENTIC_OPS_ALLOWED_OWNERS.
  3. Leave the bundle mode at staged.
  4. Keep max_repos at 1 for the first run.

Use the configuration reference only when you need the exact variable, secret, or input name.

4. Run One Staged Check

Open the installed orchestrator in GitHub Actions and select Run workflow. Set:

InputFirst-run value
target_repoThe explicit OWNER/REPO validation target
max_repos1
rollout_percent100
safe_output_modestaged
safe_output_repoLeave empty

The run should select only the named target, dispatch eligible workers, and stage proposed safe outputs without GitHub API writes.

5. Verify the Result

Before moving beyond staged, confirm:

  • authentication succeeded without exposing credential data;
  • exactly the expected target and workers were selected;
  • staged output is useful and contains a link to the orchestrator run;
  • no issue, pull request, branch, or file was written to the target;
  • AI Credit use and runtime are within the workflow limits.

If any check fails, keep the bundle in staged and use Monitor and recover to diagnose it.

Next Steps