IDE Ops dashboard
A live picture of IDE activity — change volume, workflow runs, collab, comments, and repo health.
AI
Preview — early access.
Overview
/app/ide/ops is the health dashboard for everything happening in the IDE, built from the same unified event stream (ide.* events) that drives the Chats board and Routines. It's where you go to see aggregate activity instead of one file or one chat at a time.
How it works
The page opens with a repo-divergence guard and a dispatch panel, then rolls up KPIs, human-vs-agent change volume, routine run counts, collaboration joins, and comment open/resolved counts into stat tiles. A recent-activity feed and a breakdown of events by type sit below for a closer look, and any recently blocked release lanes get their own called-out section. CKV (Creytix brain) approvals show as their own panel here too, not just the header badge.
Steps
- •
Open IDE Ops
Navigate to
/app/ide/ops, or use the link from the IDE header. - •
Check repo health first
The repo-divergence guard runs at the top of the page automatically.
- •
Scan the headline KPIs
Green, amber, and red tiles give you an at-a-glance read before you dig in.
- •
Review change volume
Human saves vs. agent edits applied vs. agent edits blocked, side by side.
- •
Check recent lane blocks
If anything was blocked from shipping, it's called out with the path and detail.
Capabilities
- Repo divergence guard — flags when the workspace has drifted from what's expected.
- Dispatch panel — visibility into dispatched work.
- Human vs. agent change volume — saves, applied edits, and blocked edits broken out separately.
- Workflow, collab, and comment stats — routine runs, collab joins, comments open/resolved.
- Recent activity and event-type breakdown — a raw look at the underlying
ide.*event stream. - CKV approvals panel — pending brain approvals, in full alongside the header badge.
Limits & honest scope
- This is a read-mostly dashboard built from the event stream — it doesn't let you undo or replay a specific action from here.
- KPI thresholds (the green/amber/red coloring) are fixed defaults, not tuned per workspace.
- If the event stream is unavailable, the page says so plainly rather than showing stale or fabricated numbers.