You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/mission-control/workflows.mdx
+28-78Lines changed: 28 additions & 78 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
---
2
-
title: "Workflows"
2
+
title: "Cloud Agent Workflows"
3
3
description: "Cloud agents that are triggered on a schedule or when events occur build automated AI workflows for your repositories."
4
4
---
5
5
6
6
7
7
<Info>
8
8
9
-
What is a Workflow?
9
+
What is a Cloud Agent Workflow?
10
10
11
-
A Workflow automatically runs an Agent on a repository when:
11
+
Mission Control Cloud Agents automatically run on a repository when:
12
12
- A schedule is reached (cron)
13
-
- An event occurs (webhook, e.g. GitHub PR)
13
+
- An event occurs (webhook, GitHub trigger)
14
14
15
-
Use Workflows for recurring or event-driven tasks like:
15
+
Use Cloud Agents for recurring or event-driven tasks like:
16
16
- Daily vulnerability scans
17
17
- Weekly changelog generation
18
18
- 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
21
21
22
22
---
23
23
24
-
## Creating a Workflow
24
+
## Creating a Cloud Agent Workflow
25
25
26
26
<Steps>
27
27
28
28
<Steptitle="Start from scratch or a template">
29
29
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).
31
31
<AccordionGroup>
32
32
33
-
<Accordiontitle="Start with a Blank Workflow">
34
-
Create a workflow from scratch by clicking Create Workflow.
33
+
<Accordiontitle="Start with a Blank Agent">
34
+
Create an agent from scratch by clicking Create Agent.
35
35
You'll choose the repository, agent, trigger type, and schedule or webhook.
36
36
</Accordion>
37
37
38
-
<Accordiontitle="Use a Workflow Template">
39
-
Select any of the “Try these Workflows” cards such as:
38
+
<Accordiontitle="Use a Template">
39
+
Select any of the “Try these Agent” cards such as:
40
40
- _Update agents.md_
41
41
- _Draft Changelog Updates_
42
42
- _Solve Snyk Vulnerabilities_
@@ -48,9 +48,9 @@ description: "Cloud agents that are triggered on a schedule or when events occur
48
48
49
49
</Step>
50
50
51
-
<Steptitle="Name the Workflow">
51
+
<Steptitle="Name the Agent">
52
52
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.
54
54
55
55
Examples:
56
56
- `Morning status check`
@@ -59,97 +59,47 @@ description: "Cloud agents that are triggered on a schedule or when events occur
59
59
60
60
</Step>
61
61
62
-
<Steptitle="Select Repository & Agent">
62
+
<Steptitle="Select Repository & Type of Kickoff">
63
63
64
64
Choose:
65
65
66
66
- 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.
72
68
73
69
</Step>
74
70
75
71
<Steptitle="Choose Trigger Type">
76
72
77
-
Pick how this Workflow should run:
73
+
Pick how this Cloud Agent Workflow should run:
78
74
79
75
- 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
-
<Steptitle="Configure the Trigger">
85
-
86
-
<AccordionGroup>
87
-
88
-
<Accordiontitle="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
-
<Accordiontitle="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)
127
78
128
79
</Step>
129
80
130
-
<Steptitle="Create the Workflow">
131
-
132
-
Click Create Cron Workflow or Create Webhook Workflow, depending on your trigger type.
81
+
<Steptitle="Create the Agent Workflow">
133
82
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).
135
84
136
85
</Step>
137
86
138
87
</Steps>
139
88
140
-
## Monitoring Workflow Runs
89
+
## Monitoring Cloud Agent Runs
141
90
142
-
Workflow runs show up just like Tasks:
91
+
Agent runs show up just like Tasks:
143
92
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.
147
96
148
97
<CardGroup>
149
-
<Cardtitle="Create a Workflow Now"icon="workflow"href="https://continue.dev/workflows">
98
+
<Cardtitle="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.
150
100
</Card>
151
101
152
-
<Cardtitle="Add an Integration"icon="workflow"href="/mission-control/integrations">
102
+
<Cardtitle="Add an Integration"icon="dashboard"href="/mission-control/integrations">
153
103
Connect GitHub, Slack, and Sentry for richer triggers and actions.
0 commit comments