Beyond Checks

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

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 vs. agents

ChecksAgents
File location.continue/checks/.continue/agents/ or continue.dev
TriggerAlways on PR openConfigurable in Mission Control
PurposePass/fail review of PRsAny automated task
Pre-configured agents you can use immediately:

Security Scanning

continuedev/snyk-continuous-ai-agent
Monitors vulnerabilities and automatically opens PRs with fixes.

GitHub Management

continuedev/github-project-manager-agent
Triages issues and manages project workflows.

Analytics Insights

continuedev/posthog-continuous-ai-agent
Analyzes user data and creates actionable tasks.

Performance Optimization

continuedev/netlify-continuous-ai-agent
Monitors Core Web Vitals and optimizes deployments.

Database Auditing

continuedev/supabase-agent
Audits RLS security and generates migrations.

Data Pipelines

continuedev/dlt-agent
Inspects pipelines and debugs load errors.
Check File ReferenceGitHub