Files
Claude-Code-Monitor/plugins/ccam-quality/commands/errors.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
List the most recent APIError events with their session and a summary [N]

List the most recent Claude Code errors from the Agent Monitor dashboard at http://localhost:4820. $ARGUMENTS is the number of errors to show (default 10).

  1. Pull recent events and keep only API errors:

    curl -s http://localhost:4820/api/events?limit=300
    

    Filter the array to event_type == "APIError". (If $ARGUMENTS is a number, show that many; otherwise show 10.) If none are found, also check curl -s http://localhost:4820/api/analytics event_types.APIError to confirm the true total and say "no recent APIError events (N total all-time)".

  2. For each error, newest first, print one line: timestamp · session_id · summary — using the timestamp, session_id, and summary fields exactly as returned (trim long summaries to ~100 chars).

  3. End with a one-line tally: total APIErrors shown and the most-affected session_id.

Output rules: cite only fields the API returned — never fabricate an error or a cause. Keep it to the list plus the tally; no extra prose. If curl cannot reach http://localhost:4820, tell the user to start the dashboard with npm start from the repo root.