README.md

Central Agentic Ops

Note

Research prototype: Features and interfaces may change.

Tip

Agents: Use the setup skill to create a control plane and the debug skill when CAO fails.

Central Agentic Ops (CAO) brings GitHub Agentic Workflow runs, costs, and outcomes into one dashboard, then adds policy-governed execution when you are ready. It operates from a control repository across explicitly enrolled repositories. CAO does not replace repository permissions, branch protection, or human review.

Start safely

Install the extension:

gh extension install githubnext/gh-cao

Git and authenticated GitHub CLI 2.68+ are required. Need a repository? Create one with gh repo create OWNER/REPOSITORY --private --clone, then cd REPOSITORY.

From the repository root:

gh cao setup

Setup makes this the control repository by preparing the monitoring runtime, policy, and gh-aw. It does not install or run a campaign, and it keeps changes local unless you separately approve commit and push. A published setup reports deployment pending; an empty dashboard is normal until Agentic Workflow evidence exists.

Use a private control repository for non-public evidence, but verify dashboard visibility before publishing: a private repository does not guarantee private GitHub Pages.

Tip

SAML-token installation failure: Use the curl installer: curl -fsSL https://raw.githubusercontent.com/githubnext/gh-cao/main/install-gh-cao.sh | bash -s -- --setup.

Follow Set Up CAO for authentication, scope, publication, and your first dashboard visit.

Add work when ready

Start with one repository in review; live outputs require explicit reviewed policy and declared safe-output capabilities. Describe the outcome and scope first—campaigns are one way to scale work, not a prerequisite. See From Outcome to Execution and the campaign catalog. You can also inspect verified Repo Assist examples without running more work.

For agents, install the CAO plugin and use the task skill: setup-cao, debug-cao, add-cao-campaign, create-cao-campaign, analyze-cao, or cao-cli.

Read the docs

• What CAO is and its safety boundaries
• CLI commands, authentication, and deployment, including GitHub Actions and Pages
• Dashboard evidence and agent analysis
• Operations, updates, and recovery
• Documentation site and compact agent context

Project

• Want to contribute? Read Contributing.
• Help keep the community welcoming: follow the Code of Conduct.
• Need support? Check out Support.
• Report vulnerabilities privately through Security.

Maintained by GitHub Next.

Acknowledgements: CAO's service design principles are inspired by SAP's Calesi pattern for CAP-Level Service Integration: domain-level interfaces, protocol-independent consumption, fast local development, interchangeable implementations, and deliberate extensibility.

Licensed under the MIT License.