Files
Claude-Code-Monitor/plugins/ccam-devtools/commands/tail-events.md
T
nntrivi2001 57dc91585d feat: Claude Code Monitor — lanes, pipelines and a merged workspace
Internal SmartGift build of a Claude Code monitoring dashboard.

Lanes: a durable unit of parallel agent work, one per working directory,
tracked across session restarts. Managed lanes are git worktrees the
dashboard provisions and can reset or remove behind a three-check destroy
guard and a counted preflight; adopted lanes are directories you already
own and are never destroyable.

Pipelines: a lane moves through pipeline stages. A stage the agent declares
with evidence renders green; a stage inferred from the tool-event stream
renders dashed amber and never counts as done. Detection is forward-only
within a 30-minute window, and never writes the declared stage.

Workspace: one page at /run with a lane grid, the selected lane's pipeline,
and a full Claude console behind a disclosure.
2026-07-30 14:39:03 +07:00

1.2 KiB

description, argument-hint
description argument-hint
Show the latest N ingested events with timestamp, event_type, and tool_name. [N]

Show the most recent events from the Agent Monitor dashboard. Argument: $ARGUMENTSN, the number of events to show (default 20).

Fetch recent events and take the newest N:

N="${1:-20}"
curl -s "http://localhost:4820/api/events?limit=${N}" | jq -r '.[] | "\(.timestamp)\t\(.event_type)\t\(.tool_name // "-")"'

The /api/events list is returned newest-first; show the most recent N. Render a compact, aligned table — one row per event:

TIME                  EVENT_TYPE     TOOL_NAME
2026-06-25T14:03:11Z  PostToolUse    Bash
2026-06-25T14:03:09Z  PreToolUse     Bash
2026-06-25T14:02:58Z  Stop           -

Include event_type (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, Notification, Compaction, APIError, TurnDuration) and tool_name when present (use - for events without a tool). End with a one-line count: Showing latest <N> events.

If the request returns a non-200 or empty body, say so and tell the user to start the dashboard with npm start from the repo root. Read-only — never POST or modify events.