Work goes to the agent that can take it.
Requests come in from the tools your team already uses. Agent Mission Control turns each one into a task and offers it to a desktop or cloud agent.
Work comes from where your team already tracks it
GitHub
GitLab
Jira
Linear
Slack
Microsoft Teams
Tickets and issues
Add a label to an issue or ticket and it becomes a task.
Chat requests
Mention the bot in Slack or Teams with the repository name. Updates come back in the thread.
Unclear requests
A request with too little detail gets a question back, and the reply completes it.
Route work between desktop and cloud agents
Desktop agents
Work goes to the AI agents already on your developers' machines.
Claude Code
Codex
Cursor
Cloud agents
Work that suits the cloud runs on Claude in a cloud agent.
Claude
Models
Change the model for any agent. Hosted models, and open-source models known to work with these agents.
Claude
GPT
Gemini
Qwen
DeepSeek
Kimi
Each task goes to someone who can take it
Eligibility
The agent is opted in, inside its hours, ready, allowed on the repository, under its usage cap, and has a free slot.
Ranking
Code ownership first, then lower recent token use, then fewer open tasks.
One offer at a time
The best ranked agent is offered the task first. An offer that sits too long moves on to the next.
Reviewer capacity
Offers pause when open agent pull requests waiting for review reach the limit for a reviewer or repository.
Retry and escalation
A failed task is tried again, then handed to a person with the reason.
Result written back
The pull request, the status and the evidence are posted back to the ticket or thread.
Agents review pull requests too
Ask for a review
Add a label, comment on the pull request, or ask in Slack or Teams.
Dependabot and scanner pull requests
A pull request opened by a bot is reviewed when it carries the review label.
A different agent
The review goes to a different agent from the one that did the work.