Captains orchestrate agent swarms
A Captain is a long-lived agent that splits your work across hundreds of threads, on any machine and any model. It reads every report and tells you only what needs you.
One agent runs the swarm
Tell a Captain what it’s for. It starts a thread for each piece of work, hears from each one when it finishes a turn, and keeps the plan current.
lisa9:02 AMShip everything in the Q4 roadmap
Captain- Readq4-roadmap.md
- Read120 issues
- Created120 threads
Splits the work
One ask becomes a thread per piece. Each thread is a full agent with its own machine, branch and pull request.
Reads every report
Each thread reports when it finishes a turn or needs something. The Captain reads them all and updates its plan.
Across your machines
Threads run in the cloud by default, or on a computer you’ve paired. Pick for every thread at once, or name a machine for one.
Cloud machines
Each thread boots its own cloud machine with your repositories checked out, so a hundred threads never share a disk.
Your own computers
Point every thread at a paired Mac, PC or build server, or say “Run this one on my Mac mini.”
Any model, your keys
Threads use the Captain’s model unless you or the Captain pick another, and they run on the subscriptions and keys you connected.
A model per thread
The strongest model for the hard refactor, a fast one for small fixes. Pick per thread, or let the Captain choose.
Your subscriptions and keys
Every thread runs as you, on your Codex, Copilot or other subscriptions and your own API keys.
Steer from anywhere
Message a Captain from the app, from Slack, or from your phone’s browser. It picks up the message wherever you sent it.
- lisa2:47 PM
@Capy captain=Mobile the TestFlight build is crashing on launch, take a look
- MobileAPP2:47 PM
Sent to Mobile.
Open in Capy
From Slack
Add captain= to a message to Capy, and it goes to that Captain instead of starting a new thread.
From any screen
Open capy.ai on your phone to read the digest and answer. Add it to your Home Screen to get push notifications.
Multiplayer by default
Captains are shared with your team, and they talk to each other. Your Captain can hand work to a teammate’s Captain or ask it what only it knows.
Shared Captains
Share a Captain with your whole organization or with specific people. Anyone it’s shared with can read it, message it and steer its threads.
Captains talk to each other
Your Captain messages any Captain you can see to hand over work or ask a question, and the answer comes back to its thread.
Orchestrations that run themselves
Ask a Captain to set up an automation, and it wakes on a schedule or when new work arrives, with nobody at the keyboard.
On a schedule
“Every weekday at 9am, check the open PRs and update the digest.” The Captain sets it up and runs it.
Work that arrives
An automation or a Slack message hands the Captain new tickets, and it starts a thread for each one.
Only what needs you
Each Captain keeps a digest of what’s waiting on you, what’s new and what’s in progress, and rewrites it as the work moves.
Tags you when it’s yours
When a decision or a blocker is yours, the Captain tags you, and the tag notifies you like any mention.
Answer in one line
Reply “merge web#136” or “hold the migration until Monday”. The Captain acts on it and drops the item.
Tracked as issues
Work lands as issues with an owner and a status, so you can see where every piece stands.
Built to last
A Captain keeps its plan, rules and digest in its own files, so it continues where it stopped, days or weeks later.
Picks up where it stopped
The plan, the working notes and the digest are files the Captain rereads every turn, not a chat it has to remember.
Rules every thread reads
“From now on, run the e2e suite before calling a PR ready.” The Captain writes the rule, and every thread follows it.
Captains beyond code
The same threads, schedules and reports run work that never opens a pull request: research, measurement, release notes and support.
lisa9:02 AMShould we switch CI providers? Report back, no code.
Captain- Read14 months of CI runs
- Compared3 providers on cost
- Wroteci-providers.md
Research and reports
Send a question, not a ticket. Threads dig in, and the Captain hands back a written report with no code.
lisa9:02 AMEvery morning, score CI health and flag anything out of band.
Captain- CI red rate
- 3%
- CI latency
- 11m
- +18%
- Oldest unmerged commit
- 4h
- Created1 thread to fix CI latency
Daily scorecard
Every morning the Captain measures what you care about, flags anything out of band and starts a thread to fix it.
lisa9:02 AMAfter each merge wave, post a changelog to #releases.
Captain- Read12 merged PRs
- Draftedthe changelog
- Postedto #releases
Changelogs in Slack
After each wave of merges, the Captain reads what shipped and posts the changelog to your channel.
lisa9:02 AMTake every bug report from #support.
Captain- Reproduced5 reports
- Filed3 issues, linked in #support
- Asked2 reporters for steps
Support queue
Every bug report in your support channel gets reproduced, filed as an issue and linked back to the person who sent it.
FAQ
Agent swarms, threads, machines, models and cost.
What is an agent swarm?+
When should I use a Captain instead of a thread?+
How do I create a Captain?+
Where do a Captain’s threads run?+
Which models can a Captain use?+
Can I steer a Captain from Slack or my phone?+
Can I limit what a Captain does on its own?+
Who can see and message a Captain?+
What does a Captain cost?+
Hand off the whole roadmap
Promote any thread to a Captain, or ask Capy to make one. It starts the threads and tells you what needs you.
