Help CenterFeaturesMultiple computers
Multiple computers
Features

Multiple computers

Q is the default name; you can rename it on its page, and the app uses the new name everywhere.

What it is

Connect the Macs you have at home and at work, and use them like one: sessions can work on any of them, and you can watch, chat and approve from any one.

When to use it

  • One computer can't run enough sessions at once, and you want another to share the load.
  • You want to close your laptop and head out, while the work carries on at home on a computer that's always on.
  • Some things are only on one computer: a signing certificate, a test phone plugged into it, the keys for a certain account.

If you only have one computer, you can skip this page for now.

A few words first

  • Computer: each Mac with QU Studio installed; the Computers page shows one card per computer. Agents run on it, using the agents you installed and signed in to on that computer, like Claude Code or Codex.
  • Main computer: the computer where Q lives. The board, memory and project list are stored once, on the main computer; other computers fetch what they need. A computer that's always on makes the best main computer.
  • Other computers: any computer other than the main one. Sessions there run as usual; board requests go to the main computer.

Before you connect

  • The other computer is also a Mac with Apple silicon.
  • Ideally, update both to the latest version. If the versions don't match, you're told which one to update first.
  • An agent, like Claude Code or Codex, is installed and signed in on that computer (see Install & sign in to agents). One is enough.
  • Only connect your own computers: a paired computer counts as you, and can operate sessions on all your computers. Sessions started and permissions changed from another computer follow what was chosen there, with no extra confirmation.

Connect another computer

  1. Open Computers (the computer button at the bottom left of the sidebar, or ⌘K and search for computers) and click Connect another computer. Everything is in one dialog: - QU Studio not installed on that computer yet: copy the download link, then download, install and open it there (the same app as this one; see Where to start). - Enter this code on that computer: this computer's pairing code, like 12-482 916, valid for 10 minutes. - Or enter the code from that computer: if the other computer showed a code, enter it here.
  2. On the other computer, open Computers → Connect another computer too, enter this computer's code (or paste the pairing link) and click Connect. Either computer can show the code; either can enter it.
  3. The computer that entered the code asks Which one is the main computer? Both are listed with their name, when they're usually on and how many projects they have. The default is the one that already has projects and is always on; if neither, the one that showed the code. - Below it, you'll see what merges where for your choice. Brand-new computers get this step too. - A repo on both computers (matched by git remote) can be merged into one project or kept as two. - Where settings differ between the two, you can pick which computer's to keep; the default is the main computer you picked. - It can't be split back automatically after merging, so read before you click OK.
  4. If you picked the computer you're on, after OK the dialog shows progress: connect to the other one → combine both computers' projects, tasks and memory → Q moves to this one. You can run it in the background.
  5. On the computer that showed the code: once the other one enters it, you see "Connected: <its name>" in green; click Next and give that computer a name (used in the sidebar and sessions), choose when it's usually on and how many tasks it may run at once, and click Done.

The number in front of the pairing code (12) comes from the relay. The relay only sees that part, never the 6 digits. A code expires after 10 minutes or too many wrong tries; click "Get a new code".

  • If this computer is already connected to a main computer elsewhere, the dialog shows no code: connect from the main computer instead.
  • If other computers are already connected to this one, it can still show a code for a new computer, but it can't enter someone else's code.

After it's added

  • Sessions: sessions on other computers show up in the sidebar, and you can read and chat in them. The session header shows which computer it runs on.
  • New projects: choose which computer a project lives on when you create it; change it later from the project's ⋯ → Change computer (the repo has to be on that computer first). You can use ~ in paths on that computer.
  • Which machines: a project can have its own copy of the code on several computers (Project settings › Which machines). The remote repo (the copy on a code host like GitHub) is the source of truth: work is merged on the computer where it was done and pushed to the remote, and the other copies pull before starting, so they're up to date.
  • Where work lands: "Run on" in task details shows the computer it actually went to, and the sidebar shows computer names too. - If you named a computer, it goes there; - if not, it follows the computer the previous step of the same request ran on; - otherwise QU compares which computer is less busy (online, on the same version, with a copy of the project or ticked under "Computers and agents to hand work to", and with a free slot) and sends it there. A move is noted in the task's activity, saying where and why; - prototype tasks always run on the computer the prototype is registered on.
  • By computer: "Projects · All computers" in the sidebar can show only the projects on one computer.
  • Limits: the limits at the bottom left can switch to another computer.
  • Max tasks at once: set it per computer on the Computers page; all agents on that computer share it. Once it's full, new tasks queue and start when a slot frees up; queued tasks also move over once another computer frees up.
  • New conversations on another computer: you can still paste screenshots and drag in files; they go straight to that computer.
  • Helpers on another computer: when the work needs a key, device or tool only another computer has, a session can call in a helper right there, working in that computer's copy of the project; in the sidebar it sits under the session that called it in.
  • Can sign releases: turn it on from each computer's menu on the Computers page. A release task (created when you say "release", or titled like "Release 0.4.28") with no computer picked only goes to a computer that has this on, is online and has a copy of the project, never just the default one; if none can take it, QU doesn't hand it out and asks you under Waiting for you, saying why. A computer whose keychain has a Developer ID certificate gets it turned on the first time it connects; after that only your choice counts. A computer you pick yourself is used as picked; if no computer has it on, handing the task out yourself still sends it to the default computer.

Cross-computer work: the project stays on one computer, an agent on another changes it

A project can stay on just one computer (the project's computer) while Claude Code or Codex on another computer works on it, without a copy of the code there.

  • Setting it up: under Project settings › "Computers and agents to hand work to", tick which computer + agent pairs this project can hand work to, and optionally set a default. Until you set it, work goes to the project's computer or a computer with a copy of the project as before; once ticked, work only goes to the ticked ones.
  • How one is picked: when a task is handed out, QU first checks whether you named one; if not, it uses the project default; if the default is full, unreachable or out of quota, it picks a ticked one with a free slot and enough quota. Computers on the same account share the same quota.
  • Who reads and writes: the agent thinks on the other computer, but reading and editing files is done by the project's computer, within what this task is allowed; task details show which computer and agent are working on it, and the changes all come from the project's computer. Refusals show the most recently refused file and why.
  • What it can't touch: secret files like .env, .git, files outside the workspace; dev-build commands and deploys; database files. To query a local database, register it first under Project settings › Data sources (SQLite only for now): the agent can only send read-only queries by name, which run on the project's computer and return just the results, up to a set limit; task details show what each task used per data source. Only you can register, change or remove data sources.
  • Checks: add checks to run (e.g. pnpm test) under Project settings › Checks; they only run once approved, and need approving again if the command changes. By default the agent on the other computer can't run them itself: when it's done it says which ones to run, and you click "Run checks" in task details. Turn it on in Rules and it can run approved checks itself in an isolated environment and fix failures it sees; the isolated copy only holds the files this task may touch, and no local databases by default.
  • Both computers need to be on 0.4.28 or later.

How computers connect

  • Directly when they can (same local network, or a different network once a direct path is found); through a relay only when they can't. A relay is a server that passes messages between two computers. On the Computers page, ⋯ → About QU on this computer shows whether it connects directly or via relay, and the latency.
  • Direct and relayed connections are both end-to-end encrypted. Relays only forward encrypted traffic and can't see your code or conversations.
  • By default QU's own relay, QU Studio Relay, is used. To keep everything on your own server, see Self-hosted relay.
  • QU Studio doesn't change your router, firewall or proxy settings. If macOS asks about the firewall, that's your call.

What happens when one is offline or asleep

  • Turn on "Push each turn to the task branch" in project settings, and after every turn the existing commits are pushed to that task's branch (nothing is committed for you, nothing goes into main). You're asked the first time it needs to push.
  • Back within 10 minutes: it carries on where it was. Back within 24 hours: it automatically redoes the interrupted turn from the start, up to 3 times.
  • If a branch fails to push, you're told why (for example, you need to sign in, or there's no remote) and what to do next, with "Push now" to try again.
  • Can't wait? "Rerun stopped sessions on another computer" moves the work to a computer that's online, pulls from the branch and redoes the interrupted turn; it checks which agents that computer has installed first. Sessions whose project doesn't allow pushing, whose branch was never pushed, or that aren't working on a task have to wait.
  • Tasks pinned to one computer (say, one wired to a test phone) don't move; they wait for it.
  • When the main computer is off or asleep, Q and the board pause too; sessions on other computers keep running.
  • While sessions are running, QU keeps the computer from falling asleep when idle (closing the lid or choosing Sleep still works). Turn this off in Settings › General.

Changing the main computer, moving projects, removing computers

  • Change the main computer: on the Computers page, ⋯ → Make this the main computer on the computer you want. Q, the board, memory and project list move there in one go; each project's sessions stay on their computers. Both computers need to be online. If it's interrupted halfway, the board is read-only until that computer reconnects and the move carries on, or you can abandon it.
  • Change a project's computer: project ⋯ → Change computer…, and enter the repo folder on that computer; the folder is checked on that computer before the move. New sessions open on the new computer from then on; existing sessions stay where they are. Not possible while tasks are still running.
  • Remove a computer: on its card, ⋯ → Remove this computer. Do this from the main computer, and move its projects off first. It disconnects right away and becomes a standalone computer; connecting it again needs pairing.

When it won't connect

The Computers page shows which of three steps the connection breaks at:

Breaks atUsuallyWhat to do
This computer to relayThe network is down, or a proxy or VPN is blocking itCheck the network; if a VPN or proxy is on, try turning it off, or switch relays in Settings
Relay to that computerThat computer is off, asleep, or not running QU StudioCheck that it's on and QU Studio is in its menu bar
HandshakeThis computer was removed there, or it was reinstalled and its key changedOn the main computer, use Connect another computer again and pair once more

"Copy diagnostics" copies all of this; attach it when you report a problem.

If another computer can't understand what this one sends (usually the two are on different QU versions), you're shown that computer's version; update both to the latest.

Remote terminal

Open another computer's terminal from this computer, or take over a session on another computer in the terminal. Only paired computers can do this; phones and tablets can't.

Turn it on at the computer being opened: off by default. On the computer whose terminal you want to open, go to Settings › Computers and turn on "Let other computers open this one's terminal". While it's off, other computers can only follow sessions there, not open its terminal. Turn it on at whichever computer you want to open; the moment it's turned off, every remote terminal open on it disconnects.

Opening one: open a terminal under a session on another computer (⌃`) and it opens on the computer running that session, marked "Remote" at the top right. Session header ⋯ → Take over in terminal works the same way.

The first time, click Allow on that computer:

  1. On this computer, click "Ask (that computer) to allow";
  2. A prompt shows in QU on that computer; click Allow there (only that computer can allow it, not another computer);
  3. Allow once, and the same person on this computer won't be asked again.

If that computer clicks Don't allow, this computer can't open it. To change that, allow it in that computer's Settings › Computers, or ask again from here.

Command log: kept on the computer being opened, under Remote terminal log at the bottom of its Computers page (it shows up once there is a log; click to expand): who, from which computer, in which session, for how long, and roughly what was typed. Kept for 30 days.

  • It's rebuilt from keystrokes, so it's approximate: commands from history (up arrow) or Tab completion may differ from what actually ran;
  • Pastes are logged only as "pasted N lines";
  • Passwords aren't logged: with echo off (typing a password) the whole line isn't logged, and nothing typed in full-screen programs like vim is logged;
  • Anything that looks like a key is masked.

Revoke: on that computer's Computers page, ⋯ → Allow remote terminals on its card lists which computers were allowed; click it to revoke. Revoking disconnects right away; a running command stops with it and won't resume. To open it again, allow it on that computer again.

When that computer can't be reached (offline or asleep), you can't open its terminal; try again once it's connected. You can still follow the session's progress.

FAQ

If I close my laptop, does the work keep running? Closing the lid puts the computer to sleep. While it's asleep, sessions on it pause, and they carry on when it wakes. To keep work running with the lid closed, hand it to a computer that's always on (like a Mac mini at home).

If two computers sign in to the same Claude account, is the quota counted twice? No. The same account's quota is counted once, and the usage page shows it combined.

Will code get passed around between computers? No. Each computer's code follows the remote repo, and work is merged on the computer where it was done. When a project stays on one computer and an agent on another changes it, reading and writing are done by the project's computer, within what the task is allowed; it can't touch secret files like .env.

Can the relay see my code? No. Direct and relayed connections are both end-to-end encrypted, and the relay only forwards encrypted content.