Skip to content

Commit e19e5da

Browse files
authored
Merge pull request #10369 from continuedev/docs/cloud-agent-workflow-replace
docs: Update Workflows docs - MVP
2 parents 7e8d8af + c91247b commit e19e5da

File tree

1 file changed

+28
-78
lines changed

1 file changed

+28
-78
lines changed

docs/mission-control/workflows.mdx

Lines changed: 28 additions & 78 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
---
2-
title: "Workflows"
2+
title: "Cloud Agent Workflows"
33
description: "Cloud agents that are triggered on a schedule or when events occur build automated AI workflows for your repositories."
44
---
55

66

77
<Info>
88

9-
What is a Workflow?
9+
What is a Cloud Agent Workflow?
1010

11-
A Workflow automatically runs an Agent on a repository when:
11+
Mission Control Cloud Agents automatically run on a repository when:
1212
- A schedule is reached (cron)
13-
- An event occurs (webhook, e.g. GitHub PR)
13+
- An event occurs (webhook, GitHub trigger)
1414

15-
Use Workflows for recurring or event-driven tasks like:
15+
Use Cloud Agents for recurring or event-driven tasks like:
1616
- Daily vulnerability scans
1717
- Weekly changelog generation
1818
- Reacting to new pull requests or Sentry alerts
@@ -21,22 +21,22 @@ description: "Cloud agents that are triggered on a schedule or when events occur
2121

2222
---
2323

24-
## Creating a Workflow
24+
## Creating a Cloud Agent Workflow
2525

2626
<Steps>
2727

2828
<Step title="Start from scratch or a template">
2929

30-
In Mission Control → Workflows, create a [new workflow](https://continue.dev/workflows/new).
30+
In Mission Control, create a [new agent](https://continue.dev/agents/new).
3131
<AccordionGroup>
3232

33-
<Accordion title="Start with a Blank Workflow">
34-
Create a workflow from scratch by clicking Create Workflow.
33+
<Accordion title="Start with a Blank Agent">
34+
Create an agent from scratch by clicking Create Agent.
3535
You'll choose the repository, agent, trigger type, and schedule or webhook.
3636
</Accordion>
3737

38-
<Accordion title="Use a Workflow Template">
39-
Select any of the “Try these Workflows” cards such as:
38+
<Accordion title="Use a Template">
39+
Select any of the “Try these Agent” cards such as:
4040
- _Update agents.md_
4141
- _Draft Changelog Updates_
4242
- _Solve Snyk Vulnerabilities_
@@ -48,9 +48,9 @@ description: "Cloud agents that are triggered on a schedule or when events occur
4848

4949
</Step>
5050

51-
<Step title="Name the Workflow">
51+
<Step title="Name the Agent">
5252

53-
Give your Workflow a clear, descriptive name.
53+
Give your Agent a clear, descriptive name, especially if your team will be managing multiple agents.
5454

5555
Examples:
5656
- `Morning status check`
@@ -59,97 +59,47 @@ description: "Cloud agents that are triggered on a schedule or when events occur
5959

6060
</Step>
6161

62-
<Step title="Select Repository & Agent">
62+
<Step title="Select Repository & Type of Kickoff">
6363

6464
Choose:
6565

6666
- Repository – the codebase the Agent will run against
67-
- Agent – the configured Agent (model, rules, tools, prompt) that should perform the work
68-
69-
<Tip>
70-
Need a new Agent? Create one in [Mission Control → Agents](https://continue.dev/agents/new), then return to this screen.
71-
</Tip>
67+
- Kickoff - whether or not the agent will run automatically on trigger or if it will be available for manual kickoff from the Mission Control UI. For example, you may want a docs agent to only run when manually kicked off on a PR, while a security agent should run automatically on a schedule.
7268

7369
</Step>
7470

7571
<Step title="Choose Trigger Type">
7672

77-
Pick how this Workflow should run:
73+
Pick how this Cloud Agent Workflow should run:
7874

7975
- Cron – run on a schedule (daily, weekly, hourly, custom)
80-
- Webhook – run when an external system sends a request (e.g. GitHub PR event)
81-
82-
</Step>
83-
84-
<Step title="Configure the Trigger">
85-
86-
<AccordionGroup>
87-
88-
<Accordion title="Cron Workflow">
89-
90-
For scheduled Workflows:
91-
92-
1. Select Cron as the trigger type
93-
2. Choose a schedule:
94-
- Common presets (e.g. weekdays at 9 AM UTC)
95-
- Hourly, Daily, Weekly, Monthly
96-
- Or define a Custom expression
97-
3. (Optional) Add additional instructions for this Workflow run in the text area.
98-
99-
Example use cases:
100-
- Run a morning status check on your repo every weekday
101-
- Refactor React components once per week
102-
- Generate a weekly changelog from recent commits
103-
104-
</Accordion>
105-
106-
<Accordion title="Webhook Workflow">
107-
108-
For event-based Workflows:
109-
110-
1. Select Webhook as the trigger type
111-
2. (Optional) Set a Secret Header (e.g. `X-Webhook-Secret`)
112-
3. (Optional) Set a Secret Value (token your external system must send)
113-
114-
You’ll receive a webhook URL to call from:
115-
- GitHub Actions
116-
- GitHub webhooks
117-
- CI/CD pipelines
118-
- Any external system that can send HTTP requests
119-
120-
Example use cases:
121-
- Run an Agent whenever a pull request is opened
122-
- Kick off a workflow when Snyk or Sentry detects an issue
123-
124-
</Accordion>
125-
126-
</AccordionGroup>
76+
- Webhook – run when an external system sends a request
77+
- GitHub Trigger – run when specific GitHub events occur (e.g. pull request opened, issue created)
12778

12879
</Step>
12980

130-
<Step title="Create the Workflow">
131-
132-
Click Create Cron Workflow or Create Webhook Workflow, depending on your trigger type.
81+
<Step title="Create the Agent Workflow">
13382

134-
Your Workflow will now appear in the Workflows list and begin running based on its configured schedule or events.
83+
Click Create Agent and now you'll be able to see, edit, and montitor it in your [Agents tab in Mission Control](https://continue.dev/agents).
13584

13685
</Step>
13786

13887
</Steps>
13988

140-
## Monitoring Workflow Runs
89+
## Monitoring Cloud Agent Runs
14190

142-
Workflow runs show up just like Tasks:
91+
Agent runs show up just like Tasks:
14392

144-
- Each execution creates a Session
145-
- Workflows appear in your Inbox
146-
- You can open the detail view to see the summary, diff, and logs.
93+
- Each execution creates a Session where you can open the detail view to see the summary, diff, and logs.
94+
- Any PR generated by the agent appears in your Inbox for review
95+
- You can also see the agents work on PRs in the PR timeline and checks.
14796

14897
<CardGroup>
149-
<Card title="Create a Workflow Now" icon="workflow" href="https://continue.dev/workflows">
98+
<Card title="Create an Agent Now" icon="robot" href="https://continue.dev/agents/new">
99+
Set up your first Cloud Agent Workflow in minutes and start automating the work you don't want to do manually.
150100
</Card>
151101

152-
<Card title="Add an Integration" icon="workflow" href="/mission-control/integrations">
102+
<Card title="Add an Integration" icon="dashboard" href="/mission-control/integrations">
153103
Connect GitHub, Slack, and Sentry for richer triggers and actions.
154104
</Card>
155105

0 commit comments

Comments
 (0)