docs/mission-control/beyond-checks.mdx
Checks review every pull request automatically. But pull requests are just one trigger. Continue can also run agents on schedules, in response to events like new issues, Sentry alerts, or Slack messages.
Agents use the same markdown file format as checks. The difference: agents can be triggered by events beyond PR open — schedules, new issues, CI failures, webhooks, and more. Triggers are configured in the Mission Control UI.
| Checks | Agents | |
|---|---|---|
| File location | .continue/checks/ | .continue/agents/ or continue.dev |
| Trigger | Always on PR open | Configurable in Mission Control |
| Purpose | Pass/fail review of PRs | Any automated task |
Pre-configured agents you can use immediately:
<CardGroup cols={2}> <Card title="Security Scanning" icon="shield-check" href="https://continue.dev/continuedev/snyk-continuous-ai-agent"> `continuedev/snyk-continuous-ai-agent`Monitors vulnerabilities and automatically opens PRs with fixes.
Triages issues and manages project workflows.
Analyzes user data and creates actionable tasks.
Monitors Core Web Vitals and optimizes deployments.
Audits RLS security and generates migrations.
Inspects pipelines and debugs load errors.