Note
Research prototype: Features and interfaces may change as the project evolves.
Tip
Agent setup router: When asked to create, bootstrap, initialize, or set up a Central Agentic Ops control plane, load and follow the setup skill. Use a separate control repository by default; any repository may explicitly run workflows it maintains in-tree as a source-managed control plane, including a catalog dogfooding its own workflows.
Tip
Agent debugging router: When a CAO deployment, credential, Agentic Workflow, Activity collection, or dashboard build fails, load and follow the debug-cao skill. Preserve the failing workflow commit and exact component versions before changing or rerunning the deployment.
Run trusted agentic operations across your repository fleet from one central control plane.
Bootstrap an empty control repository with:
curl --fail --silent --show-error --location \
https://raw.githubusercontent.com/githubnext/gh-aw-cao/main/install.sh |
bashThe installer adds gh-aw and the core CAO campaign, creates the minimal control policy, and makes the repository-local ./cao.sh CLI executable. It makes no CAO changes when rerun after installation. Install the Agent Plugin separately when you want the portable CAO skills.
Central Agentic Ops provides persistent agentic campaigns that continuously pursue defined outcomes across explicit repository fleets without copying workflows into every repository.
- Reach more repositories: deterministically discover and batch inventories of 100,000+ repositories while keeping each run bounded.
- Roll out with confidence: review proposed outcomes away from the target, then promote each campaign independently to
live. - Keep work accountable: every worker stays scoped to one repository and links its outcome to the originating control-plane run.
Central Agentic Ops extends GitHub Agentic Workflows with a catalog of reusable campaigns and a central control plane for explicit repository fleets. It does not replace repository permissions, branch protections, or human review.
See the open issues for current work and planned improvements.
Ready to explore? See the docs.
This repository is an Agent Plugins 1.0 plugin. It exposes the portable setup-cao, debug-cao, add-cao-campaign, create-cao-campaign, analyze-cao, and cao-cli skills.
Install this repository using any compatible client's plugin installer, then invoke setup-cao to create a control plane from scratch, debug-cao to diagnose deployment failures and prepare evidence-rich issues, add-cao-campaign to discover and safely install an existing catalog campaign, create-cao-campaign with an operational strategy and target-repository description, analyze-cao to download and query CAO activity data with the cao CLI, or cao-cli for a general reference on using cao in local development and inside agentic workflow runs.
In Copilot CLI, the plugin also provides a Central Agentic Ops Canvas. Open it to start the repository's local dashboard preview, optionally for a specified OWNER/REPOSITORY. The extension gives the agent tools to execute declarative queries with the canonical dashboard query engine and read bounded sections of the dashboard data architecture specification.
The default Central Agentic Ops campaign installs the dashboard builder and manual Pages publisher. Before running Central Agentic Ops Dashboard for the first time:
- Open Settings > Pages in the control repository.
- Under Build and deployment, set Source to GitHub Actions.
- Restrict Pages access to the intended audience before publishing control-plane data.
The dashboard workflow remains manual and does not enable Pages automatically.
Contributions and issue reports are welcome. Read CONTRIBUTING.md and our Code of Conduct before participating.
Central Agentic Ops is maintained by GitHub Next. Ownership rules are recorded in .github/CODEOWNERS.
See SUPPORT.md for help and support expectations. Report suspected security vulnerabilities privately by following SECURITY.md.
This project is licensed under the MIT License. See LICENSE for the full terms.