executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
live-watchPolls the Agent Monitor /api/stats endpoint several times over a short window and reports the live deltas in active_sessions, active_agents, events_today, and ws_connections so you can see activity moving in real time. Use when watching the dashboard for live changes rather than a one-time snapshot.
Independent GitHub snapshot · Automated classification · Original documentation governs
Watch the dashboard's live counters change over a short window by polling
/api/stats a few times and reporting the deltas.
The user provides: $ARGUMENTS
Interpreted as the watch shape: number of polls and/or interval (e.g. 5x3s =
5 samples 3 seconds apart). Defaults when empty: 5 samples, ~3 seconds apart
(a ~15-second window). A bare number means that many samples at the default
interval; a bare duration means the default sample count at that interval.
| Endpoint | Returns |
|---|---|
GET /api/stats (polled) | { total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status } |
Poll GET /api/stats once per interval for the configured number of samples,
recording the timestamp and the four watched counters each time. Pace the polls
with a short wait between requests; keep the total window short (seconds, not
minutes) so it stays interactive.
If the very first poll fails to connect, the dashboard is down — stop and tell
the user to start it with npm start (or npm run dev) from the repo root,
then retry.
State the sample count, interval, and total elapsed window.
A Markdown table — one row per poll — with columns:
#, time, active_sessions, active_agents, events_today, ws_connections.
For each of the four watched counters, report the net change from the first to
the last sample using ▲ (increase), ▼ (decrease), or = (no change). Note any
mid-window spikes or dips visible in the timeline.
One line: is the dashboard actively receiving traffic (counters moving) or idle (flat) over the window?
events_today: ▲ +7.