Skip to main content

​
What You Can Do in Mission Control

Mission Control is where developers and teams use Continue to power everyday coding workflows. From quick one-off Tasks to fully automated pipelines, everything starts here.

Create & Run Tasks

Trigger your AI Agents and review or approve the results.

Manage Your Agents

Create, configure, and monitor your custom Agents across repositories.

Set Up Workflows

Schedule recurring Tasks, connect webhooks to trigger Agents automatically, or add

Connect Integrations

Link GitHub, Slack, and Sentry to power your Tasks and Workflows.

​
Monitoring & Insights

Track performance, share configurations across your organization, and monitor agent activity in real time.

Metrics

Measure success rates, PR activity, and intervention trends across Agents.

Organization Sharing

Share Agents and Workflows with teammates using built-in access controls.

Agent Monitoring

View active runs, logs, and outcomes for every Agent session.

​
Components Behind Mission Control

Mission Control uses your configured components to power Agents, Tasks, and Workflows: Agents are built from reusable components that you can create, share, and customize:

Models

Large Language Models from various providers (OpenAI, Anthropic, etc.) configured for specific roles like chat, autocomplete, or editing

MCPs

Model Context Protocol servers that provide tools and capabilities like database access, web search, or custom functions

Rules

Guidelines that shape AI behavior - coding standards, constraints, or specific instructions for your domain

Prompts

Reusable instructions for common tasks, optimized for specific workflows or coding patterns
Components are the building blocks for agents that you can create new or remix from an existing component. When you create a component in mission control, it becomes available according to the permissions you set: Personal, Public, or Organization.
Some components can receive values, including secrets, as inputs through templating. For values that the user needs to set, you can use template variables (e.g. ${{ inputs.API_KEY}}). Then, the user can set API_KEY: ${{ secrets.MY_API_KEY }} in the with clause of their agent or config.
Choosing between secrets. and inputs.When creating components for your Agent:
  • Use ${{ inputs.INPUT_NAME }} in your definition when you want users to be able to customize which secret is used
  • Users will then map their own secrets using ${{ secrets.SECRET_NAME }} in the with clause
For personal or single-use configurations, you can skip the inputs layer and reference ${{ secrets.SECRET_NAME }} directly.

​
Get Started