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.
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).
-
Pull recent events and keep only API errors:
curl -s http://localhost:4820/api/events?limit=300Filter the array to
event_type == "APIError". (If$ARGUMENTSis a number, show that many; otherwise show 10.) If none are found, also checkcurl -s http://localhost:4820/api/analyticsevent_types.APIErrorto confirm the true total and say "no recent APIError events (N total all-time)". -
For each error, newest first, print one line:
timestamp · session_id · summary— using thetimestamp,session_id, andsummaryfields exactly as returned (trim long summaries to ~100 chars). -
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.