| title | At a glance | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| description | See what is moving, what needs attention, and whether the evidence is ready for follow-up. | ||||||||||
| agent |
|
The dashboard is the operational view of your Central Agentic Ops control plane. It turns retained activity evidence into focused views, each designed to answer a specific question:
- What work is moving now?
- What has reached the repositories in scope?
- What needs attention or a closer look?
- Is the evidence complete and current enough to act on?
Every view follows the same data flow:
- Activity collects evidence. The Activity workflow publishes a bounded snapshot of workflow activity.
- The selected backend prepares and queries the data. Static Pages uses a browser Web Worker and IndexedDB; local Go serving uses SQLite; hosted Go serving uses PostgreSQL. Each evaluates Dashboard Language.
- The active view presents the result. When the underlying data changes, the query runs again and the view updates.
The dashboard is not a live feed. It reads the latest snapshot collected by the Activity workflow. Data ingestion follows that evidence into each query backend, while the Data model explains the records and relationships available to every view.
On the first visit to a static dashboard, a dismissible import screen explains how the browser downloads and caches its first snapshot. Dismissing it keeps the import running; Overview continues to show preparation progress rather than calling campaigns idle. The import screen is automatically removed when a complete snapshot is ready, and its animation timers and progress subscription are released. If preparation fails or is cancelled while the screen is still open, it shows a Retry import action. Explore data or Escape dismisses the screen; Overview cannot reopen it after dismissal. Later visits use the cached snapshot during refresh. Go-backed dashboards do not use this browser-local first-import experience and do not fall back to it on failure.
Treat each result as a starting point for investigation, not as a scorecard. A high count, a quiet period, or a warning tells you where to look next. Before following up, check the availability, completeness, and freshness shown with it:
- Empty means the dashboard has evidence and found no matching activity.
- Unavailable means the dashboard could not obtain the evidence it needs.
- Partial means the result may describe only part of the campaign.
- Stale means newer activity may not be represented yet.
These distinctions keep missing information from looking like a healthy zero.
See the Glossary for definitions of Dashboard terms such as rollout mode, safe output, outcome, and operational value.
Reading dashboard evidence does not start work, approve an output, grant workflow authority, change rollout policy, or write to a repository. Make those decisions through the control repository and its reviewed workflows and policy. Static Pages is read-only; optional canvas commands and hosted CLI actions have separate authorization and approval requirements.
The canvas Query editor supports local AI-assisted authoring and saved views. It is not enabled on the static website, hosted server, or ordinary local preview.
Maintenance → Governance is visible only to an authorized hosted
administrator with a current, assured session. It is hidden in published
dashboards, local Go previews and Copilot canvases, including through direct
links. The standalone Node --admin mode has been retired.
Hosted repository installation tokens cannot administer organization or
enterprise variables, so this editor remains disabled there. Use gh aw env
outside the dashboard with administrative credentials for the exact chosen
scope. Review sets and deletions before applying, verify saved variables and
recompile workflows to incorporate changed compiler defaults.
Organization and enterprise variables are inherited by repositories with access
to them, including CAO repositories, but may also affect repositories outside
CAO. Existing narrower overrides and variable access lists remain in effect.
null or omitted keys remove an override at the selected scope, not an inherited
default. Visibility controls access for newly created variables only.
This page manages non-secret GitHub Actions variables, not secrets, rollout policy, or live authority. Never enter credentials in the YAML. The chosen scope requires administrative access; hosted repository installation tokens cannot perform these operations, so editing remains disabled for hosted administrators.
- Start with Overview to understand the default operational view.
- Choose where to host the dashboard in Deployment options.
- Read Data ingestion to follow evidence from GitHub Actions into the browser.
- Use the Data model to understand entities, relationships, identities, and retention.
- Build views with the Dashboard Language guide, then consult the language specification and view catalog for complete reference material.
- Let browser agents read the same pages through WebMCP, and agents without a browser or shell through Agent analysis.
- Use the Copilot plugin and canvas for local query authoring and explicitly approved commands.