Agents

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.

Local agents vs. cloud agents

There are two ways to define agents:
  • Local: Place agent files in .continue/agents/ in your repository. Version-controlled and shared with your team.
  • Cloud: Created and managed on continue.dev/agents. Web UI for configuration, no file to commit.
Both run on Continue's cloud infrastructure.

Triggers

Triggers determine when an agent runs. They are configured in Mission Control.
Supported trigger types:
TriggerDescription
CronRun on a schedule (daily, weekly, hourly, custom)
WebhookRun when an external system sends a request
GitHub eventRun when specific GitHub events occur (PR opened, issue created, label added, etc.)
Version-controlled trigger configuration (defined in the agent file itself) is on the roadmap. Today, all triggers are managed through Mission Control.

Running agents

Trigger agents from the web interface at continue.dev and review results in real-time.

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: