Cloud Agent Workflows
Cloud agents that are triggered on a schedule or when events occur build automated AI workflows for your repositories.
What is a Cloud Agent Workflow?
Mission Control Cloud Agents automatically run on a repository when:
- A schedule is reached (cron)
- An event occurs (webhook, GitHub trigger)
Use Cloud Agents for recurring or event-driven tasks like:
- Daily vulnerability scans
- Weekly changelog generation
- Reacting to new pull requests or Sentry alerts
Creating a Cloud Agent Workflow
1
Start from scratch or a template
In Mission Control, create a new agent.
2
Name the Agent
Give your Agent a clear, descriptive name, especially if your team will be managing multiple agents.
Examples:
Morning status checkWeekly changelog draftDaily Snyk vulnerability scan
3
Select Repository & Type of Kickoff
Choose:
- Repository – the codebase the Agent will run against
- 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.
4
Choose Trigger Type
Pick how this Cloud Agent Workflow should run:
- Cron – run on a schedule (daily, weekly, hourly, custom)
- Webhook – run when an external system sends a request
- GitHub Trigger – run when specific GitHub events occur (e.g. pull request opened, issue created)
5
Create the Agent Workflow
Click Create Agent and now you'll be able to see, edit, and montitor it in your Agents tab in Mission Control.
Monitoring Cloud Agent Runs
Agent runs show up just like Tasks:
- Each execution creates a Session where you can open the detail view to see the summary, diff, and logs.
- Any PR generated by the agent appears in your Inbox for review
- You can also see the agents work on PRs in the PR timeline and checks.