Skip to main content

​
What are Cloud Agents?

Cloud Agents are AI workflows that execute on remote infrastructure (Continue Mission Control) rather than your local machine. Because they live in the cloud, they maintain persistent, secure connections to your development tools and can be triggered in two ways:
  • On-Demand: Manually triggered via Chat, Tasks, or the CLI for complex, human-guided work.
  • Automated: Automatically triggered by schedules (Cron) or events (Webhooks) for background maintenance.
Unlike local assistants, Cloud Agents provide a centralized “Mission Control” where teams can collaborate on tasks, review shared logs, and standardize automation across repositories.

Agents in Continue

Agents are custom AI workflows that combine a prompt, rules, and tools (MCPs and more) to complete specific, repeatable tasks. They live in the Continue Mission Control and can be executed from Mission Control (web interface), TUI mode, or headless automation.

​
Ways to Run Cloud Agents

These execution modes allow Continue agents to function as cloud agents, running continuously, headlessly, or on schedules without requiring a developer in the loop:
Interactive web interfaceTrigger from the Continue Mission Control and review results in real-time.
# Navigate to hub.continue.dev/agents
# Click "Run Agent" on any agent
# Monitor progress and review outputs
Perfect for: Interactive debugging, reviewing agent outputs, team collaboration

​
Local vs. Cloud Agents

FeatureLocal Agents (IDE / TUI)Cloud Agents (Mission Control)
Compute LocationYour Local MachineRemote Cloud Infrastructure
Primary Use Casefast, private iteration and “single-player” codingCollaborative tasks, heavy processing, and reliable automation
Context AccessLimited to open files and local git stateFull repository access + integrated tools (Sentry, Snyk, etc.)
TriggersManual Tasks / CLIHybrid: Manual Chat, Cron Schedules, or Event Webhooks
AvailabilityStops when you close your laptopAlways On: Runs asynchronously in the background

​
Pre-configured Cloud Agents

Skip the setup and use battle-tested agents from our cookbook collection:

🔒 Security Scanning

continuedev/snyk-continuous-ai-agentA cloud agent that monitors vulnerabilities and automatically opens PRs with fixes.

🐛 GitHub Management

continuedev/github-project-manager-agentA cloud agent that triages issues and manages project workflows

📊 Analytics Insights

continuedev/posthog-continuous-ai-agentA cloud agent that analyzes user data and creates actionable tasks

⚡ Performance Optimization

continuedev/netlify-continuous-ai-agentA cloud agent that monitors Core Web Vitals and optimizes deployments

🗄️ Database Auditing

continuedev/supabase-agentA cloud agent that audits RLS security and generates migrations

🔄 Data Pipelines

continuedev/dlt-agentA cloud agent that inspects pipelines and debugs load errors
Explore More Cloud Agents: Browse the complete collection of pre-configured agents and MCP integration cookbooks in our Guides Overview.

​
Collaboration

Agents are organizational assets — once created, everyone in your org can use them:
RolePermissions
PublicUse, create, remix, and delete Agents
OrganizationShare agents with your team
PrivateCreate, edit, and delete Agents for your personal use

​
Getting Started

1

Try a Pre-configured Agent

Start with a cookbook agent like continuedev/github-project-manager-agent:
cn --agent continuedev/github-project-manager-agent "List open issues labeled bug"
2

Practice with TUI Mode

Test agents locally before automation:
cn --agent continuedev/snyk-continuous-ai-agent
# Interactive mode - perfect for learning how to use the agent for your use case
3

Create Your First Agent

Ready to build custom workflows? Learn how in our Create and Edit guide.
4

Set Up Automation

Integrate with CI/CD using headless mode and webhooks for continuous workflows.

​
Monitoring

You can monitor all activity for your Agents directly in Mission Control.
The Inbox shows every Task or Workflow run, and you can filter by Agent.
Click any session in the Inbox to open the Detail page.Each session includes:
  • Summary — what the agent did and why
  • Diff — generated code changes
  • Logs — full execution trace, tool calls, and reasoning
This is the best way to review output, debug issues, or confirm correctness.
All monitoring is scoped to your current workspace.

​
Best Practices

The practice of using cloud agents, which we call Continuous AI, requires forethought to set up the right guardrails:
  • Start Small: Begin with tasks you’re confident Continue can accomplish
  • Use Thorough Prompts: Agents can run for extended periods, so invest in detailed instructions
  • Test Locally First: Practice with TUI mode before deploying to production
  • Team Alignment: Discuss agent usage and adjust code review habits for higher PR volume
  • Iterate and Improve: Be willing to refine prompts based on results

​
Next Steps

Create an Agent

Build your first custom agent with prompts, rules, and tools

Explore Cookbooks

Browse pre-built agents for security, analytics, and more

CLI Guide

Learn to run agents from the command line

Mission Control

Access the web interface to manage agents