A crew of coding agents,
on all your Macs.

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.

Download for macOS

What it does

• One server, every Mac

  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.

  Mac miniin the closet

  • fix-loginworking
  • websiteworking
  • deployneeds you
  • searchin review

  MacBook Air

  iMac

  MacBook Pro

  lid closed

  • Live on every screen. Answer a question on the laptop and it's gone from the iMac the same second.
  • Close the lid. The crew lives on the server, so shut the laptop and come back to finished work.
  • From anywhere. byre talks over Tailscale, so the closet Mac is one click from the coffee shop.

• Every server, every project

  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.

  byre

  • mac-mini3 projects

  • byre
  • website
  • infra

  • studio2 projects
  • build-box5 projects

  MacBook Air

  mac-ministudiobuild-box

  new Mac Studio

  mac-ministudiobuild-box

  first launch, synced through iCloud

  • Already there. Servers sync through iCloud, so a new Mac finds them all on first launch.
  • One window. Switch between every server and all of its projects without leaving it.
  • Color-coded. Each server wears its own color, so you always know which one you're on.

• Tasks

  Every task gets its own git worktree, branch and port block. Talk to its agent in a live transcript, even mid-turn.

  fix-login⎇ byre/fix-loginown worktreeports 41000–41009

  website⎇ byre/websiteown worktreeports 41010–41019

  search⎇ byre/searchown worktreeports 41020–41029

  fix-login

  Moving sessions to the new table and copying the old rows across…

  keep the old column until the migration ships

  Got it, I'll leave legacy_id in place and finish the copy.

  working

  • Isolated. Its own worktree, branch and ports, so parallel tasks never collide.
  • Talk mid-turn. Message the agent while it works and it takes the note on board.
  • As many as you like. Start another whenever an idea strikes; they all run at once.

• Lead agent

  One long-running agent watches every task, points you at what needs you, and starts, messages, merges or discards tasks when you ask.

  Lead

  Three tasks need you:

  • deployhas a question about cache lifetime
  • websiteis ready to merge
  • searchgot two review findings

  merge website, and start a task to add dark mode to the docs

  Merging website now. Started docs dark mode; I'll tell you when it needs you.

  • Watches everything. Every task's turns, questions and reviews pass by the lead.
  • Knows what needs you. It tells you which tasks are waiting on you, and why.
  • Does the legwork. Ask it to start, message, merge or discard tasks, and it does.

• Questions, not interruptions

  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.

  deploy · question

  How long should the download page be cached?

  1 hourfresh, more load

  1 dayrecommended

  1 weekstale after a release

  byre · deploy

  How long should the download page be cached?

  • Options laid out. Every choice comes with what you get and what you give up.
  • A recommendation. The agent always says which option it would pick, and why.
  • Never miss one. A notification lands the moment a question does, a click away.

• Cross-vendor reviews

  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.

  Claude Code turn→snapshot 3→Codex review→agent triages

  search · review of snapshot 3

  Port block isn't freed when a task is discardedmedium

  fixingReleasing it in the discard path.

  Rename cfg to configlow

  ignoringMatches the surrounding code.Fix it anyway

  • A second opinion. Each turn that changes files is read by the other vendor's model.
  • Triaged for you. The agent fixes what holds up and explains what it leaves.
  • Your call. Overrule any finding it skipped with one click and it gets fixed.

• One-click merge

  The agent merges main in and resolves conflicts, then byre squashes, pushes and closes the task.

  avatars

  ready to merge Let people upload a profile photo Photos are cropped to a square and resized, and initials show until one is set. Merge

  5 turns on byre/avatars1 commit on main

  • Conflicts handled. The agent merges main in and works through any conflicts.
  • One clean commit. The whole task lands on main as a single squashed commit.
  • Then it's done. byre pushes and closes the task, so your list stays short.

• Snapshots and forks

  Step through a task's snapshots, diff any of them, and fork a new task from any one, conversation included.

  #1#2#3#4#5

  new task

  search: try SQLite FTS instead

  forked from #3, conversation included

  diff #3 → #5

  index/build.go+48 −12

  index/query.go+21 −30

  docs/search.md+9 −2

  • Every step kept. Each turn that changes files leaves a snapshot behind it.
  • Diff anything. Compare any two snapshots to see exactly what each turn did.
  • Fork the past. Start a new task from any snapshot, conversation included.

• Teams and workflows

  Agents spawn subtasks or share a worktree as a team. Workflows chain stages with fan-out and fan-in.

  planone agent

  build apiClaude Code

  build appCodex

  write docsAntigravity

  reviewall three, together

  • Subtasks. An agent hands off pieces of work to new agents on their own branches.
  • Teams. Several agents share one worktree and build the same change together.
  • Workflows. Save a pipeline once: stages fan out, fan back in, and run again.

• Hands on your Macs

  Agents can see and drive the Mac byre runs on, and the Macs you have the app open on, when a task needs it.

  your app · on the iMac

  Sign in

  Emailada@example.com

  Password••••••••

  Sign in

  Signed in as Ada

  fix-login

  fix-login

  found the Sign in window

  typed a test email

  typed the password

  clicked Sign in: it works

  • Sees the screen. Agents read screenshots and every window's controls.
  • Drives the Mac. They click, type and browse to try what they just built.
  • Your Macs too. Any Mac with byre's app open can lend the agents a hand.

Getting started

1. Download byre and click Run byre on this Mac.
2. Open it on every other Mac you own. Your crew is already there.