File a coding ticket from your phone and have a home Mac open a pull request for it.
Manage a small fleet of Mac workers running Claude Code from one dashboard.
Review and approve every merge with automated CI checks still enforced.
Try the whole ticket to merge workflow in a simulated fake mode with no setup.
| phyolim/outerloop | 0marildo/imago | 0xdfi/glm-5.2-1m-4x-dgx-spark | |
|---|---|---|---|
| Stars | 3 | 3 | 3 |
| Language | Python | Python | Python |
| Setup difficulty | moderate | easy | hard |
| Complexity | 3/5 | 2/5 | 5/5 |
| Audience | developer | general | researcher |
Figures from each repo's GitHub metadata at analysis time.
Real coding work needs Claude Code, GitHub CLI, and git configured on each worker Mac.
Outerloop turns the Mac computers you already own into a small group of Claude Code workers you manage from a single web dashboard. One always on Mac acts as the hub, holding the ticket queue, scheduler, and dashboard, while any other Mac can join as a worker that picks up tasks. A single Mac can act as a complete setup by itself, since the hub also does its own coding work. The problem it addresses is that the machine capable of doing coding work is often not the one in front of you. Your desk Mac might have Claude Code logged in with repositories cloned and git configured, but if you think of a fix while on your phone, options used to be an awkward remote session or writing the idea down for later. With outerloop you file a ticket from wherever you are, and a capable machine at home picks it up, so you come back later to a finished pull request. The basic unit of work is a ticket. One agent writes code on a branch using the ticket as context, a separate agent reviews that code, and the resulting pull request references the ticket. The reviewer cannot merge its own approval, and even after a human approves a merge, failing automated checks still block it. Machines discover each other on your local network, or connect through an outbound connection to a low cost server when you are away, without a VPN or cloud service. Everything is managed through a web dashboard, with an inbox of things needing your attention, a board listing every ticket, a fleet view of your machines, and a full activity log. As a ticket moves along, an agent may pause to ask a question, or request a tool permission you can allow or deny, and you always get the final say on approving, requesting changes to, or rejecting a pull request before it merges. Installing the menu bar app through Homebrew is the recommended way to start, and it handles setup like the dashboard password and pairing for you. Any Mac doing coding work also needs Claude Code, GitHub's CLI, and git configured with a commit identity. You can also try the workflow without installing real tools, since cloning the repository starts a fake mode that simulates the agents and GitHub end to end using only Python.
Turns your own Mac computers into a small fleet of Claude Code workers managed from one web dashboard for filing and reviewing coding tickets.
Mainly Python. The stack also includes Python, Claude Code, Homebrew.
No license information is stated in the README.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.