About convex-monitor
convex-monitor is a skill that waits for the next typed event instead of repeatedly polling. It races local error logs, deployment subscriptions, and Sentinel production-error rows, and returns the first event or a quiet heartbeat.
Key features
- 01Waits for typed events
- 02Combines local logs, deployment subscriptions, and Sentinel rows
- 03Returns the first event or a quiet heartbeat
- 04Falls back to polling where blocking MCP is unavailable
Use cases
- 01React to Convex errors as they appear
- 02Triage Sentinel production errors
- 03Handle feature requests through a shared event flow
MCP support
It prefers a blocking MCP tool for waiting on events; where that is unavailable or weak, it uses a polling loop with the same event contract.
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ convex/ agent-skills --skill convex-monitorAfter installing, type/convex-monitorin Claude Code to confirm it loaded.
Details
From the project READMEWatch for the next thing to react to
Block on the next typed event instead of polling. Races local error logs, deployment subscriptions, and Sentinel prod-error rows; returns the first to fire (or a quiet heartbeat).
Workflow
- Call
wait_for_eventwith {project_dir, event_kinds, timeout_ms}. - On kind=convex_error/next_error: decode and fix it. On kind=prod_error: triage (see sentinel) and fix. On kind=feature_request: build it. On kind=quiet: loop.
- Where a harness has no blocking MCP (e.g. Copilot cloud), the pack runs a poll loop with the SAME event contract — same behavior, different mechanism.
Rules
- Prefer the blocking tool; fall back to a poll loop only where blocking MCP is weak.
- The event schema is fixed and versioned — the same trigger yields the same typed event.
- Prod events (kind=prod_error) require a deployed cloud app plus Sentinel.
Comments
Markdown supported