Convex Monitor

by get-convex2cfe645c87f9No license63 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 6 days ago

Watch for the next dev/prod error or request in a Convex app and react to it.

Instructions onlyDevOps & Cloud

AI-generated overview

Blocks on the next typed Convex app event — dev or prod error, or feature request — and reacts to it.

What it does: This skill describes a workflow for waiting on the next typed event in a Convex app instead of polling. It calls a wait_for_event tool with project directory, event kinds, and a timeout, racing local error logs, deployment subscriptions, and Sentinel production-error rows, and returns the first event to fire or a quiet heartbeat. Depending on the event kind, the agent decodes and fixes errors, triages production errors, builds feature requests, or loops on quiet. Where blocking MCP is unavailable, it falls back to a poll loop with the same event contract.
When to use it: Use it when working in a Convex project and you want the agent to react to the next development or production error, or to a feature request, rather than repeatedly polling. It suits harnesses that support a blocking MCP tool, with a poll-loop fallback for environments where blocking is weak.
Requirements: Requires a Convex project directory and the wait_for_event tool, ideally via a blocking MCP harness; production events require a deployed cloud app plus Sentinel. No scripts are shipped — instructions only.

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

Call wait_for_event with {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.

Source and attribution

Source:get-convex/agent-skillsinskills/convex-monitorat commit2cfe645

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Convex Monitor

Watch for the next thing to react to

Workflow

Rules

Source and attribution

More from get-convex/agent-skills

Convex Verify

Convex Test

Convex Suggest

Convex Sentinel

Convex Self Heal

Convex Seed

More in DevOps & Cloud

M5 Onboard

Spanner Basics

Secops Cases

Managed Airflow Migrations

Managed Airflow Dag Troubleshooting

Iam Helper For Privileged Access Management