Who it is forA developer maintaining several repositories who wants backlog items moving in each project at once.
The problemWorking through several repositories one chain at a time leaves most of the machine and subscription capacity idle.
The outcomeChains for different projects and tasks progress in parallel, limited only by machine resources and subscription rate limits.
What you need first
- An Apple Silicon Mac or a Linux machine (Ubuntu 24.04 LTS verified)
- Node.js satisfying ^20.19.0 || ^22.13.0 || >=24, with 22.17.0 from .nvmrc and npm 10.9.2 or later
- Docker Compose and Git
- The official Codex CLI, signed in under the account that runs the runner (Claude Code and Pi optional)
- A test repository to try it on before pointing it at real work
Steps
- Add each repository as a project following the pull-request workflow guide.
- Queue one or more specs per project on the board.
- Register additional runners if you want more throughput, keeping within your machine and subscription limits.
- Watch the board and answer Inbox questions as they appear, since each chain pauses until a human decision is given.
Prompt for your agent
Using the mosonlab/anneal repository, queue one spec for each of the projects <project-a> and <project-b> on the board, then report which chains are running at the same time. Verify that both chains advance without waiting on each other.
Caveat. The README gives no concurrency numbers, so the practical limit depends on your own machine and your provider plan limits.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for mosonlab/anneal and "Run chains for several projects at the same time"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer