<metaname="description"content="Run many coding agents in parallel on one Mac, each on its own branch, with a lead agent that keeps track of them for you, and drive them from every Mac you use.">
<h1>A crew of coding agents, <br><span>on all your Macs.</span></h1>
<pclass="lede">byre runs Claude Code, Codex and Antigravity side by side on one Mac, each on its own branch and worktree, with a lead agent that watches them all and tells you what needs you. Pick up from whichever Mac you're at.</p>
<summary><h3>One server, every Mac</h3><p>The agents run on one Mac that stays on, such as a Mac mini in a closet. Open byre on your laptop, your desk Mac, or all of them at once: each shows the same tasks, questions and transcripts live. Close the laptop and the agents keep working.</p><spanclass="more"></span></summary>
<divclass="detail">
<divclass="fig diagram"aria-hidden="true">
<divclass="win server">
<divclass="label">Mac mini<span>in the closet</span></div>
<li><strong>Live on every screen.</strong> Answer a question on the laptop and it's gone from the iMac the same second.</li>
<li><strong>Close the lid.</strong> The crew lives on the server, so shut the laptop and come back to finished work.</li>
<li><strong>From anywhere.</strong> byre talks over Tailscale, so the closet Mac is one click from the coffee shop.</li>
</ul>
</div>
</details></li>
<liclass="wide purple"><detailsname="feature">
<summary><h3>Every server, every project</h3><p>Your servers sync through iCloud, so a new Mac finds them on first launch. Switch between servers in one window, each with as many projects as you like and its own color.</p><spanclass="more"></span></summary>
<divclass="detail">
<divclass="fig split"aria-hidden="true">
<divclass="win servers">
<divclass="bar"><i></i><i></i><i></i>byre</div>
<divclass="body">
<ul>
<liclass="row on purple"><i></i><b>mac-mini</b><spanclass="end">3 projects</span></li>
<divclass="win synced"><divclass="bar"><i></i><i></i><i></i>new Mac Studio</div><divclass="body"><spanclass="chip purple"><i></i>mac-mini</span><spanclass="chip cyan"><i></i>studio</span><spanclass="chip orange"><i></i>build-box</span></div></div>
</div>
<divclass="caption">first launch, synced through iCloud</div>
</div>
</div>
<ulclass="points">
<li><strong>Already there.</strong> Servers sync through iCloud, so a new Mac finds them all on first launch.</li>
<li><strong>One window.</strong> Switch between every server and all of its projects without leaving it.</li>
<li><strong>Color-coded.</strong> Each server wears its own color, so you always know which one you're on.</li>
</ul>
</div>
</details></li>
<liclass="green"><detailsname="feature">
<summary><h3>Tasks</h3><p>Every task gets its own git worktree, branch and port block. Talk to its agent in a live transcript, even mid-turn.</p><spanclass="more"></span></summary>
<li><strong>Isolated.</strong> Its own worktree, branch and ports, so parallel tasks never collide.</li>
<li><strong>Talk mid-turn.</strong> Message the agent while it works and it takes the note on board.</li>
<li><strong>As many as you like.</strong> Start another whenever an idea strikes; they all run at once.</li>
</ul>
</div>
</details></li>
<liclass="orange"><detailsname="feature">
<summary><h3>Lead agent</h3><p>One long-running agent watches every task, points you at what needs you, and starts, messages, merges or discards tasks when you ask.</p><spanclass="more"></span></summary>
<divclass="detail">
<divclass="fig"aria-hidden="true">
<divclass="win">
<divclass="bar"><i></i><i></i><i></i>Lead</div>
<divclass="body">
<divclass="msg">Three tasks need you:
<ul>
<liclass="row red"><i></i><b>deploy</b><spanclass="muted">has a question about cache lifetime</span></li>
<liclass="row orange"><i></i><b>website</b><spanclass="muted">is ready to merge</span></li>
<liclass="row cyan"><i></i><b>search</b><spanclass="muted">got two review findings</span></li>
</ul>
</div>
<divclass="msg you">merge website, and start a task to add dark mode to the docs</div>
<divclass="msg">Merging website now. Started <b>docs dark mode</b>; I'll tell you when it needs you.</div>
</div>
</div>
</div>
<ulclass="points">
<li><strong>Watches everything.</strong> Every task's turns, questions and reviews pass by the lead.</li>
<li><strong>Knows what needs you.</strong> It tells you which tasks are waiting on you, and why.</li>
<li><strong>Does the legwork.</strong> Ask it to start, message, merge or discard tasks, and it does.</li>
</ul>
</div>
</details></li>
<liclass="wide red"><detailsname="feature">
<summary><h3>Questions, not interruptions</h3><p>When an agent needs a decision, it lays out the options and recommends one. A notification brings you straight to it; pick an answer and the agent carries on.</p><spanclass="more"></span></summary>
<divclass="option">1 week<spanclass="muted">stale after a release</span></div>
</div>
</div>
<divclass="notif">
<divclass="app"></div>
<div>
<b>byre · deploy</b>
<divclass="muted">How long should the download page be cached?</div>
</div>
</div>
</div>
<ulclass="points">
<li><strong>Options laid out.</strong> Every choice comes with what you get and what you give up.</li>
<li><strong>A recommendation.</strong> The agent always says which option it would pick, and why.</li>
<li><strong>Never miss one.</strong> A notification lands the moment a question does, a click away.</li>
</ul>
</div>
</details></li>
<liclass="wide cyan"><detailsname="feature">
<summary><h3>Cross-vendor reviews</h3><p>Every turn that changes files is reviewed by the other vendor's model. The agent fixes the findings it agrees with on its own and says why it skips the rest; you can overrule any of them with a click.</p><spanclass="more"></span></summary>
<divclass="bar"><i></i><i></i><i></i>search · review of snapshot 3</div>
<divclass="body">
<divclass="finding red"><i></i><b>Port block isn't freed when a task is discarded</b><spanclass="chip">medium</span><divclass="reply"><spanclass="chip green on">fixing</span>Releasing it in the discard path.</div></div>
<divclass="finding orange"><i></i><b>Rename cfg to config</b><spanclass="chip">low</span><divclass="reply"><spanclass="chip">ignoring</span>Matches the surrounding code.<spanclass="btn ghost">Fix it anyway</span></div></div>
</div>
</div>
</div>
<ulclass="points">
<li><strong>A second opinion.</strong> Each turn that changes files is read by the other vendor's model.</li>
<li><strong>Triaged for you.</strong> The agent fixes what holds up and explains what it leaves.</li>
<li><strong>Your call.</strong> Overrule any finding it skipped with one click and it gets fixed.</li>
</ul>
</div>
</details></li>
<li><detailsname="feature">
<summary><h3>One-click merge</h3><p>The agent merges main in and resolves conflicts, then byre squashes, pushes and closes the task.</p><spanclass="more"></span></summary>
<divclass="legend"><span>5 turns on byre/avatars</span><span><b>1 commit on main</b></span></div>
</div>
</div>
<ulclass="points">
<li><strong>Conflicts handled.</strong> The agent merges main in and works through any conflicts.</li>
<li><strong>One clean commit.</strong> The whole task lands on main as a single squashed commit.</li>
<li><strong>Then it's done.</strong> byre pushes and closes the task, so your list stays short.</li>
</ul>
</div>
</details></li>
<liclass="green"><detailsname="feature">
<summary><h3>Snapshots and forks</h3><p>Step through a task's snapshots, diff any of them, and fork a new task from any one, conversation included.</p><spanclass="more"></span></summary>
<li><strong>Every step kept.</strong> Each turn that changes files leaves a snapshot behind it.</li>
<li><strong>Diff anything.</strong> Compare any two snapshots to see exactly what each turn did.</li>
<li><strong>Fork the past.</strong> Start a new task from any snapshot, conversation included.</li>
</ul>
</div>
</details></li>
<liclass="orange"><detailsname="feature">
<summary><h3>Teams and workflows</h3><p>Agents spawn subtasks or share a worktree as a team. Workflows chain stages with fan-out and fan-in.</p><spanclass="more"></span></summary>
<li><strong>Subtasks.</strong> An agent hands off pieces of work to new agents on their own branches.</li>
<li><strong>Teams.</strong> Several agents share one worktree and build the same change together.</li>
<li><strong>Workflows.</strong> Save a pipeline once: stages fan out, fan back in, and run again.</li>
</ul>
</div>
</details></li>
<liclass="purple"><detailsname="feature">
<summary><h3>Hands on your Macs</h3><p>Agents can see and drive the Mac byre runs on, and the Macs you have the app open on, when a task needs it.</p><spanclass="more"></span></summary>
<divclass="detail">
<divclass="fig hands"aria-hidden="true">
<divclass="split">
<divclass="win screen">
<divclass="bar"><i></i><i></i><i></i>your app · on the iMac</div>
