Convex Sentinel

by get-convex2cfe645c87f9No licenseListed Oct 8, 2026Updated Oct 8, 2026

Set up Sentinel production error capture in your own Convex deployment.

Instructions onlyDevOps & Cloud
AI-generated overview

Sets up Sentinel production error capture inside a user's own Convex deployment, with redaction and optional triage.

What it does
Guides installation of the @convex-dev/sentinel component in a Convex project, wiring the client SDK with a React error boundary and global error handlers plus breadcrumbs. It covers write-time redaction, reading recent errors through the Convex CLI, and reacting to new errors via the monitor's prod_error event. An optional self-healing cron can classify errors and hand recurring non-transient ones to ai-runner to open a fix pull request.
When to use it
Use it when a Convex application needs production error capture that stays inside the user's own deployment. It fits teams that want server function failures, client JS/React crashes, and OCC or scale signals recorded and triaged without sending data to a third party.
Requirements
A Convex project and deployment, the @convex-dev/sentinel component, and the Convex CLI for reading error data. Capturing production errors requires a deployed cloud app, while installation works anonymously. The optional self-healing cron depends on ai-runner. No scripts ship with the skill; it is instructions only.
<!-- GENERATED from convex-agents content/capabilities/sentinel.json — do not edit by hand. -->

Capture production errors in your own deployment

Install @convex-dev/sentinel to capture production errors (server function failures, client JS/React crashes, OCC and scale signals) into a table in the user's OWN deployment, redacted at write time, then react to new ones. Data never leaves the user's deployment.

Workflow

  1. Install the component: app.use(sentinel) in convex/convex.config.ts.
  2. Wire the client SDK: a React error boundary plus window.onerror/unhandledrejection and breadcrumbs.
  3. Redaction runs at write time and is on by default (default-deny on secret key names and value patterns).
  4. Read recent errors with the Convex CLI (convex data, run-once-query); react to new ones via the monitor's prod_error event.
  5. Optionally enable the self-healing cron: triage classifies each error and, for recurring non-transient ones, hands it to ai-runner to open a fix PR.

Rules

  • Redaction is mandatory and on by default — never store raw secrets; the agent's reads reach the model provider.
  • Data stays in the user's deployment; never send it to a third party.
  • Sample and cap to control volume and cost.
  • Capturing PROD errors needs a deployed cloud app; install works anonymously.

Source and attribution

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

License: No license

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

Report or request removal