Operator Layer
Agents Monitoring
Operator Console for Live Agent Systems
A control-room dashboard for watching real agents, live sessions, sync health, and task linkage on a single host. It is designed for operators who need to know what is running, what is blocked, and what requires intervention.
Live
Runtime projection
Single host
Conservative first scope
Visible
Degraded sync and blocked work
Operator console
A dashboard for running agents, not demoing them
Operator questions
01
Why operators need this
Once agents are doing real work, the bottleneck shifts to operations. Teams need to see active runs, stale agents, task linkage, and sync failures without digging through raw CLI output or transcripts. Without an operator surface, automation becomes harder to trust than manual work.
What is running right now?
The console is optimized to answer this directly without requiring transcript spelunking or raw CLI output.
Which agents are stale, blocked, or offline?
The console is optimized to answer this directly without requiring transcript spelunking or raw CLI output.
Which sessions are linked to tracked work and which are unmapped?
The console is optimized to answer this directly without requiring transcript spelunking or raw CLI output.
Is sync healthy or degraded?
The console is optimized to answer this directly without requiring transcript spelunking or raw CLI output.
02
Operator model
Built a local-first operator console that projects live OpenClaw and plan-store sources into one read model. The app reconciles live runtime state, persists the last good snapshot, exposes operator APIs, and pushes changes over SSE. Instead of generic CRUD screens, it organizes the UI around summary, attention queue, run detail, tracked tasks, and sync health so the operator can make decisions quickly.
runtime summary and sync health banner
Each view is designed around operator decision-making rather than generic CRUD navigation.
configured-agent roster including idle agents
Each view is designed around operator decision-making rather than generic CRUD navigation.
active session table with linkage state
Each view is designed around operator decision-making rather than generic CRUD navigation.
tracked task board and attention queue
Each view is designed around operator decision-making rather than generic CRUD navigation.
privacy-safe detail views for agents, runs, and tasks
Each view is designed around operator decision-making rather than generic CRUD navigation.
03
Attention semantics
The attention queue is intentionally opinionated. It surfaces sync warnings, blocked runs, stale or offline agents, blocked tasks, and active work that cannot be linked deterministically to tracked tasks.