What Is Central Agentic Ops?

You have workflows triaging issues in one repository and investigating failures in another. Central Agentic Ops (CAO) helps you understand and operate this work across repositories: observe activity, evaluate available cost and outcome evidence, and coordinate the execution and rollout of shared workflows. Existing workflows stay with their owners; shared work does not require moving every workflow into one central repository.

GitHub Agentic Workflows (AWs) are AI-powered workflows that run in GitHub Actions. You describe a task in Markdown, and an agent carries it out with configured tools and permissions. They can respond to events, run on a schedule, or be requested on demand. CAO monitors these workflows, not every ordinary Actions job. Learn about GitHub Agentic Workflows.

Set up CAO and monitor your workflows. Connect one repository to get started.

What you can do today

Capability	What it gives you
Observe activity	See collected activity across configured repositories, inspect recorded runs, and follow them back to GitHub.
Evaluate results	Inspect costs, outputs, and outcomes where evidence is available. Use them to investigate what the work produced, not just whether it ran.
Scale and roll out shared work	Standalone workflows and campaigns can opt into admission and bounded rollout across explicitly allowed repositories. In review mode, proposals go to a review destination; target repositories stay unchanged until live output is explicitly authorized.

Workflows can stay repository-local, be shared across projects, or run centrally. Campaigns are one opinionated way to package, scale, and roll out shared work, not the only operating pattern. Integrated review and rollout controls also support standalone agentic workflows, but do not apply automatically to every observed workflow.

For example, after an issue-triage workflow runs, you can inspect its run and follow the collected evidence to see what it produced. The dashboard helps you investigate whether the work was useful; a green run alone does not answer that. A successful run is not automatically a successful outcome. Missing cost or outcome evidence is not proof of zero cost or success.

See the product

1 2 3

Public sample, 19 October 2026, after import completed. Not a live feed. Open full-size capture.

1. Start with your repositories. See configured projects in one place.
2. Read activity. Ranked bars compare distinct retained runs. Zero means no retained runs, not confirmed inactivity.
3. Follow outputs. Inspect retained issue outputs; output counts alone do not prove successful outcomes.

Explore the public Repositories view. Wait for import to finish before reading the charts. See the dashboard guide for more.

How evidence reaches the dashboard

A control repository is an ordinary GitHub repository that stores your CAO configuration, holds credentials in Actions secrets, and runs collection and participating shared workflows.

CAO Activity collects read-only evidence from the repositories you configure and publishes a snapshot for the dashboard:

flowchart TB
  accTitle: Monitoring existing agentic workflows
  accDescr: CAO Activity collects read-only evidence from configured repositories and publishes a snapshot for the shared dashboard. Observation grants no write authority.
  workflows["Existing AWs"] -->|"Read evidence only"| activity["CAO Activity"]
  activity -->|"Collected snapshot"| dashboard["Shared dashboard"]

The dashboard shows collected evidence, not a live feed. Collection can be partial or stale; an empty chart does not establish that no workflows ran. See CAO Activity for collection and data-quality details.

Essential safety boundaries

• Seeing is not authorizing. Observing a workflow grants no write authority. Collecting evidence does not change its permissions or authorize writes.
• Local owners keep control. Project workflows and review requirements stay with their owners. A shared dashboard does not transfer credentials or authority.
• Public means public-safe. Use a public control repository only when its configuration, run metadata, dashboard data, evidence, and review outputs can be public. A private repository does not by itself guarantee private Pages; setup checks publication visibility.

Get started

Set up CAO and monitor your workflows. Connect a repository to see its existing evidence.

Explore workflow operating patterns and ownership or browse campaigns for shared tasks and rollout.