Dashboards

Colony Cloud provides operator surfaces under the Dashboard group in the left navigation. This page documents Pipeline, Reporting, and Inbox in full. For the ambient Live view (/dashboard/pipeline-live) and the Reviews inbox, see their dedicated pages: Live and Reviews.

Pipeline

Route: /dashboard/pipeline

Pipeline is the first screen after sign-in and the primary daily-use surface. It shows active work flowing through stations, organized per repository, as a real-time swim-lane board.

Each repository gets its own swim lane. Within the lane, issues appear as cards at their current station — analyzing, planning, in-review, and so on. The view updates on a live connection; no manual refresh is needed.

Tip

Sort by age descending to surface issues that have been in the same state for an unusually long time. Issues that have not transitioned in more than a few hours are candidates for operator intervention.

For a state-machine grid showing every pipeline state as a count node — and list and board views scoped to individual states — see the Pipeline Live surface at /dashboard/pipeline-live.

Reporting

Route: /dashboard/reporting

Reporting is the home for the org’s sealed, dated record of what happened — an evidence-dated statement band above a ledger of reports. Until a report has sealed, both the band and the ledger say so in words rather than showing a zero or a placeholder number.

Note

The prior Insights page (fleet KPIs, cost breakdowns, and cycle-time forensics) has been retired. Reporting will gain its first statements as the report object lands.

Inbox

Route: /dashboard/inbox

Note

Both /attention (without the /dashboard/ prefix) and /dashboard/attention are permanent redirects to /dashboard/inbox. Bookmarks and external links using either short form continue to work.

Inbox surfaces issues that require operator action — the subset of the pipeline that the autonomous recovery protocols could not resolve on their own. Issues in the Needs you section are sorted by urgency: blocked and awaiting-external first, then awaiting operator action, then review-ready, then issues that are merely stuck.

Inbox sections

Section	What appears here
System Alerts	LLM health warnings and operational alerts affecting the fleet as a whole.
Strategy proposals awaiting review	Strategist-proposed snapshots that need operator approval before becoming active.
Recurring failures	Error patterns appearing across two or more issues — a signal of systematic problems in conventions, CI, or environment configuration.
Needs you	Individual issues that have stalled, are blocked, are awaiting human code review, or need other direct operator intervention.

Common interventions

From the Inbox, you can act directly on each issue:

Situation	Action
Worker stalled or timed out	Click Retry to clear the block, reset failure counters, and re-enqueue. A sub-menu lets you optionally select a complexity-tier override (equivalent to /colony:retry [size]).
Issue is blocked on a dependency that has since resolved	Click Unblock to remove the current block and re-enqueue.
Review loop caused by a bad issue or bad conventions	Fix .colony/conventions.md, then click Retry.
Issue should be abandoned	Click Cancel to transition to Done and close the GitHub issue.
Issue has related dead-letter context	Diagnose the issue, then use Recover a Dead-Lettered Issue when the record itself must be retried or resolved.
Processing should halt temporarily without losing state	Click Pause to pause processing while preserving current state.
Issue was previously paused and should resume	Click Resume to unpause and restore to the pre-pause state.
Analysis is complete and planning should be skipped	Click Skip planning to go straight to development.
Issue scope is too large and should be broken into subtasks	Click Decompose to force epic decomposition into subtasks.
Current implementation is wrong and should be restarted from scratch	Click Reimplement to close the PR, delete the branch and worktree, and reset to analyzing.
PR is ready for a re-review cycle	Click Trigger review to start a new review cycle.
PR needs targeted changes the automated reviewer cannot capture	Click Return with feedback to send change-request text back to the developer agent.
Pipeline state is incorrect and must be corrected manually	Click Override state to manually set the pipeline state to any valid state.
Issue priority needs to change	Click Set priority to set priority to high, normal, or low.

For a full list of slash commands available on individual issues and PRs, see the Operator role.