Live control surface
Sign in to load the current snapshot.
Last sync: —
Merge + push approval gate
Telemetry / 01
Worker operations, at a glance.
One developer cockpit for live runs, pool pressure, and review-ready workspace state.
Host pulse
Resource pulse
source unavailable
No telemetry
Resource telemetry
Waiting for the authenticated resource feed.
Current agents
No data
Who is working now
Current agent telemetry
Sign in to load current agents.
Pool capacityWaiting for telemetry
unknown
Configured limit is authoritative on the server.
—in flight
—available
—queued
—configured max
Usage telemetry
No telemetry
Run usage and performance
Token volume
aggregate across runsExecution performance
duration and retry pressureSign in to load usage and performance statistics.
Operations / 02
Dispatch ledger
Ten runs per page. Select a row to reveal its live console directly beneath the record.
Dispatch ledger
— runsRecent runs
Run telemetry is unavailable.
| Run | State | Repository / branch | Settings | Updated |
|---|
Select a run to attach its live console.
Sign in to open the ledgerThis private-use surface requires an active session.
No runs match this viewThe run ledger is empty or your current filter has no matches.
Prompt, interrupt, cancel, and terminal input are authenticated development controls. Merge and push approval actions remain gated.
Registry / 03
Registered repositories
Worker-visible checkouts, branch policy, and repository-specific controls.
Private repository registry
—Available checkouts
| Repository | Local checkout | Working branch | Discovered / allowed branches | State | Actions |
|---|
Controls / 04
Run intent and policy
Global pool policy stays here; repository controls live in the Repositories tab.
Operator shortcuts
Repository controls moved
Register checkouts, tune Jira pickup fields, or start a custom runner from a repository record.
Global policy
server authoritativePool dispatch
Authenticated development controls remain available. Merge and push approval actions remain gated.
This UI never accepts bearer tokens. Username/password session authentication and the server-side approval gate remain in force.