Every coding agent you pay for. One workspace.

Yes. It is signed with a Developer ID and notarized by Apple, so it opens like any other app. If an older download says it is damaged or cannot be verified, download it again.

Claude Code, Codex and Antigravity. Relaycrew finds whichever of claude, codex and agy are installed and signed in on your machine. It does not include or resell any of them.

Yes, through Claude. When a task mentions Chrome, a browser, a tab, a website or a link, the Claude step can open pages, click, fill in forms and read what is on screen in your own Chrome. Install Anthropic's Claude in Chrome extension and sign in with the same Claude account first.

No. There are no Relaycrew servers. It runs the agent programs already on your computer, and each one talks to its own provider exactly as it does when you run it yourself. If you switch on phone control, what you send from the phone, the plan and the last lines of activity pass through Google's Firebase so the phone can show them.

It puts quota you'd otherwise lose to work. Later saves a task instead of running it now. When one of your subscriptions is within an hour of resetting with at least a quarter unused, Relaycrew runs the oldest saved task without asking, in a separate copy of the project on a new git branch, and commits the result there. Your working files are never touched; the side panel shows the branch, and you merge it if you like it. It needs a git project, and you can switch it off in Settings.

Yes, while Relaycrew is open on your Mac. In Settings, under Phone, switch on control from your phone, choose how long the phone stays connected (one hour up to four days) and click Pair a phone, then scan the code with the phone's camera. When the time is up, the phone is cut off until you pair it again. The phone can send tasks and commands, approve or cancel plans, stop a task and follow its progress. A paired phone can run anything you could type on the Mac, so only pair your own, and use Unpair all phones if one is lost. Phone control is off by default.

You approve the plan first. After that, agents edit files and run commands (tests, builds) in the folder you ran the task in without asking again, so use it in a project under version control. If you don't like the result, Undo puts the files back.

Yes, in a git project. Before each step Relaycrew takes a snapshot of every file git can see, including ones you haven't committed. In the task panel, Undo task puts everything back as it was before the task, and Undo from this step keeps the earlier steps. It works the same whichever agent made the change, and it leaves your staging area, branches and commits alone; files git ignores aren't touched. Edits you made after the task are undone too (you're warned), and Redo brings it all back. From a terminal: relaycrew --undo. Snapshots last about two weeks.

A quick planner looks at what each agent is good at, how much quota each has left, and this project's track record: which agent finished or failed which steps here before. That record is a plain file, .relaycrew/record.md, that you can read or delete. If a step still fails, it moves to the next agent.

How much each subscription window moved while the task ran, from the usage figures Claude and Codex report themselves. It's shown when the task ends and in the task panel. Anything else using the same subscription at the same time, like a chat in another window, counts too.

Short notes and a log of finished tasks, as plain text files in a .relaycrew folder inside each project. You can read, edit or delete them, and switch the feature off in Settings.

It is an early build. The installer exists, but the list of running agents and typing tasks in plain words are not wired up on Windows yet.