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 with Cloud Agents (AI-powered).

Create & Run Tasks

Trigger your AI Agents and review or approve the results.

Manage Your Cloud Agents

Configure, run, and monitor your custom Cloud Agents across repositories.

Connect Integrations

Link GitHub, Slack, Sentry, and more to power your Cloud Agents.

​
Inbox: One Place to Triage, Assign, and Take Action

The Inbox is your team’s central queue for all Cloud Agent powered Tasks, activity, and first-class integrations like Sentry and Snyk. It gives developers a shared place to review work, delegate responsibility, and launch follow-up Tasks—all without leaving Mission Control.

Unified View

See every incoming Task, Sentry alert, Snyk vulnerability, and workflow output in one place.

Powerful Filtering

Slice the Inbox by Agent, repository, integration, creator, status, or time to surface what matters now.

Clear Ownership

Assign Sessions to teammates so responsibilities are explicit and reviews move forward.

Take Action Fast

Launch follow-up Tasks, investigate errors, or generate fixes directly from the Inbox—no context switching.

​
First-Class Integration Tabs

Some signals deserve their own dedicated view. When you connect integrations:
See error events organized by project with occurrences, first/last seen timestamps, and one-click Solve actions that launch an Agent to investigate or generate a fix.
Review high-severity vulnerabilities, check CVSS scores, and trigger Agents to patch or upgrade dependencies.

​
Monitoring & Insights

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

Metrics

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

Organization Sharing

Share Cloud Agents with teammates using built-in access controls.

Cloud Agent Monitoring

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

​
Components Behind Mission Control’s Cloud Agents

Cloud 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

Tools

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

Rules

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

Prompts

Reusable instructions for common tasks, optimized for specific workflows or coding patterns
When you create a component for your Cloud Agent 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