docs/agents/overview.mdx
Agents use the same markdown file format as checks. The difference: agents can be triggered by events beyond PR open — cron schedules, GitHub issues, Sentry alerts, Slack messages, webhooks. Triggers are configured in Mission Control.
There are two ways to define agents:
.continue/agents/ in your repository. Version-controlled and shared with your team.Both run on Continue's cloud infrastructure.
Triggers determine when an agent runs. They are configured in Mission Control.
Supported trigger types:
| Trigger | Description |
|---|---|
| Cron | Run on a schedule (daily, weekly, hourly, custom) |
| Webhook | Run when an external system sends a request |
| GitHub event | Run when specific GitHub events occur (PR opened, issue created, label added, etc.) |
Opens an interactive chat session with the agent.
Runs the agent non-interactively. Useful for CI/CD pipelines and scheduled automation.
| 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.