mcpField
C
convex-monitor

convex-monitor

github.com/get-convexCloud & DevOps6931.1k installsUpdated 1d ago
Repository

About convex-monitor

convex-monitor is a skill that waits for typed events from local error logs, deployment subscriptions, and Sentinel production-error rows. It returns the first event or a quiet heartbeat, using polling only when blocking MCP is unavailable or weak.

Key features

  1. 01Waits for the next typed event
  2. 02Races local logs, deployments, and Sentinel errors
  3. 03Returns a quiet heartbeat when no event arrives
  4. 04Uses polling when blocking MCP is unavailable

Use cases

  1. 01React to a local Convex error as it appears
  2. 02Triage production errors reported by Sentinel
  3. 03Handle feature requests from the event stream

MCP support

The skill uses a blocking MCP tool, wait_for_event, to receive typed events. In environments where blocking MCP 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/get-convex/agent-skills --skill convex-monitor

After installing, type/convex-monitorin Claude Code to confirm it loaded.

Details

From the project README

Watch 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

  1. Call wait_for_event with {project_dir, event_kinds, timeout_ms}.
  2. 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.
  3. 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