convex-monitor

Watches for errors and requests in Convex apps and reacts to typed events.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/Tehzeeb07/CodeRush --skill convex-monitor-tehzeeb07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convex-monitor
Source: https://github.com/Tehzeeb07/CodeRush/tree/main/.agents/skills/convex-monitor
Command: npx skills add https://github.com/Tehzeeb07/CodeRush --skill convex-monitor-tehzeeb07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers running Convex apps need to catch dev errors, production failures, and feature requests as they happen, but manually polling logs and dashboards is slow and easy to miss. This Skill blocks on the next typed event and returns it for immediate triage or fixing. ## Core Features & Use Cases - Blocking Event Wait: Calls wait_for_event with project directory, event kinds, and timeout to race local error logs, deployment subscriptions, and Sentinel prod-error rows, returning the first to fire. - Typed Event Handling: Decodes and fixes convex_error/next_error events, triages prod_error events via Sentinel, builds on feature_request events, and loops on quiet heartbeats. - Poll-Loop Fallback: Where a harness lacks blocking MCP (e.g., Copilot cloud), it runs a poll loop with the same versioned event contract. - Use Case: While developing a Convex app, let the agent block on the next error event; when a runtime error fires, it is decoded and fixed automatically without you watching the terminal. ## Quick Start Watch my Convex project for the next error or feature request and react to it when it fires.

Frequently Asked Questions about convex-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor a Convex app for errors automatically?▼

Call wait_for_event with your project directory, the event kinds you care about, and a timeout in milliseconds. It races local error logs, deployment subscriptions, and Sentinel prod-error rows, returning the first typed event to fire.

How to react to production errors in a Convex deployment?▼

Subscribe to prod_error events, which come from Sentinel rows in a deployed cloud app. When one fires, triage it using the Sentinel workflow and then apply a fix, following the same typed event contract as local errors.

Does Convex event monitoring work without blocking MCP support?▼

Yes. In harnesses without blocking MCP, such as Copilot cloud, the skill runs a poll loop instead. The poll loop uses the same versioned event schema, so behavior and event handling remain identical.

What event types can a Convex monitor wait for?▼

It supports convex_error or next_error for local failures, prod_error for deployed app issues via Sentinel, feature_request for new work, and quiet heartbeats when nothing fires within the timeout.

When does Convex prod error monitoring not work?▼

Prod error events require a deployed cloud app plus Sentinel configured. Without that deployment, only local error and feature request events are available, and prod_error events will never fire.