| title | What is Central Agentic Ops? | ||||
|---|---|---|---|---|---|
| description | Monitor and govern GitHub Agentic Workflows across repositories, with shared evidence and policy-controlled execution. | ||||
| next |
|
Central Agentic Ops (CAO) is a system for monitoring and governing GitHub Agentic Workflows (AWs) across repositories. It brings collected activity, cost, and outcome evidence into a shared dashboard and supports policy-governed execution and rollout of participating shared workflows.
Agentic work might begin with a single task, then grow across repositories. AWs run those tasks in GitHub Actions, using Markdown instructions and configured tools and permissions. These AWs form the building blocks of CAO as we scale.
- Observe activity. CAO Activity collects a bounded, read-only snapshot from explicitly configured repositories for dashboards, reports, and agents. Existing workflows keep running where they are.
- Evaluate results. Follow runs and outputs back to GitHub; check freshness and completeness and accepted outcomes, not just run success. Missing evidence is not a healthy zero.
- Govern shared work when needed. Explicitly integrated workflows run
under reviewed control-repository policy. Start with one target in
review, inspect the proposal, and authorize live output separately.
Monitoring existing workflows does not move them or change their permissions. When you choose to govern shared automation, describe the outcome, target scope, and execution requirements; guidance and authoring agents derive the simplest structure. Campaigns are one way to package and scale work, not a prerequisite. See From Outcome to Execution.
An issue-triage workflow runs in one repository while another investigates failures elsewhere. CAO shows their collected runs and available outputs in one place, with links back to GitHub. A successful run is not automatically a successful outcome. The evidence helps you investigate what the work produced.
Public sample, 19 October 2026. Collected evidence, not a live feed.
Explore the public Repositories view.
CAO governs explicitly integrated workflows, not every observed AW or ordinary Actions job. Review is real execution and can create proposals in the review destination; live output requires explicit authorization. Missing required authority, access, or evidence fails closed.