Put your agents to work while you sleep
Give an agent a queue of tasks. It works through all of them in a sandbox, runs your checks, self-reviews, and leaves the results for you to approve.
{{providers}}-
Queue up the work
Add tasks from your terminal or from any editor that supports ACP, or let your agents file what they find. Each task is a folder that says what to do and how to tell it's done.
88% of real requests to coding agents gave only the problem, with little else, against 7% of benchmark tasks, a 2026 study found.
-
A fresh agent for every task
The loop works through the queue one task at a time. Each task starts a fresh agent session, without the previous task’s conversation.
39% average drop when top models got a task over several turns instead of in one message, a 2025 study found.
-
Checked and committed
The agent runs your checks before it calls a task done, then commits the work: one commit per task.
22.6% of the failures found in 20,574 real coding-agent sessions were the agent claiming it was done too early, a 2026 study found.
-
Accounts rotate when rate limited
When an account reaches its usage limit, the loop carries on with the next one.
20 hours a week is how long the average Claude Code user now has it running, Anthropic found.
-
Questions don't stop the work
If a task needs your decision, the agent records the question, options and recommendation. The loop continues with the other tasks.
92.3% of coding-agent session time went to waiting on the person, a 2026 study of 4,300 sessions found.
-
Reviewed before you wake up
A final review checks completed work against each task’s requirements and reopens tasks that need more work.
About half of agent pull requests that passed the tests still wouldn't have been merged by the project's maintainers, METR found.
-
Good morning
Review the commits, answer the waiting question, and queue tonight's work.
1,300+ pull requests merged at Stripe each week are written start to finish by unattended agents and reviewed by people, Stripe reported.
Safe to leave running
- {{check}}Your project is mounted; your home folder is not.
- {{check}}Known secret files appear empty.
- {{check}}Filtered networking: your AI provider and approved destinations.
- {{check}}Your host Git credentials stay outside the box.
42% of reported coding-agent file mishaps reached outside the project, into system files, personal files and secrets, a 2026 study found.
The loop and the sandbox are just the start. co:op gives you these too.
-
{{services}}
Project services
Run Postgres, Redis and other supported Compose services beside the box, each in its own container.
In filtered mode, approved services use a private network with no direct internet access. Secret files stay hidden unless you approve access.
6.5 s to start the box with Postgres and Redis beside it, once their images are pulled, we measured.
-
{{team}}
Presets
A preset is a team of models: one lead, and as many roles as you need. The lead consults them or hands them work.
coop presets initwrites a starter team you can change.+18 points on competitive programming problems when Claude reviewed Codex's drafts, against +13 when Codex reviewed its own, a 2026 study found.
-
{{fork}}
Forks
Hand work to agents, each in its own copy of your project, and keep working in yours.
Review a fork like a pull request, then merge it. Set a project gate to check the rebased work before merging.
16 agents in their own copies, each task claimed by one, built a 100,000-line C compiler that builds Linux, Anthropic reported.
-
{{integrations}}
Integrations
Use Zed’s agent panel to plan work and add tasks to the queue.
Any editor that speaks ACP works too, with account rotation built in.
Get started
Free and open source. Runs on macOS and Linux with Docker.