Your studio here.
The work on any computer.
Put the AigoPilot agent on a Mac or another Windows PC, pair it with six digits, and its sessions sit in the same list as your own.
Some work needs a particular machine. An iPhone app needs Xcode, and Xcode needs a Mac. A Unity project might live on the laptop with the better graphics card. The agent lets that computer do the work while you keep prompting, approving and reading from the studio on your main PC.
The same program, started as an agent, with a small window and an icon in the tray or the menu bar. It starts when you sign in to the computer and runs in your own user session, so editors such as Unity have a screen to draw on.
A small window on the other computer shows its name, that it is ready, its address and the studio it is paired with. The six digits appear on request. It also shows what is installed there, with buttons to install and sign in, a tick to start with the computer, the update, and a card for a project that is arriving, with its progress and a detailed log. The agent's window is in English only.
The agent shows six digits for five minutes. Type them into the studio and you are done. After three wrong tries it makes new ones.
Agents announce themselves on the local network and appear under “Add a computer”. Typing an address is still there if you need it.
One encrypted connection stays open to each computer. If it drops, it reconnects on its own, and it finds a computer that came back on a new address or port. On a home network a request took about 5.6 ms.
Projects and sessions from all your computers sit side by side, each marked with its computer's name and colour. A computer that is switched off goes pale instead of vanishing.
Start, continue, prompt, answer and stop sessions on the other computer as if they were local. Pictures you paste are sent to that computer.
If the other computer is missing Claude Code or Codex, AigoPilot installs it with the provider's own installer after one yes, without admin rights. The CLI's own sign-in opens on that computer and closes when you are done.
Browse the other computer's folders from the studio and add a project from there.
Each computer has its own permission mode, and the title bar always names the mode of the computer the open project is on.
Each agent looks at aigopilot.com once a day, and at once when you press “Check for updates” in its window. A newer build is fetched, checked against its signature and put in place when no session is in the middle of work. This works on Windows and on a Mac, and it has been seen on a real Mac: about fifty seconds after the button was pressed, the new build was running. The version of each computer is shown next to its name.
The usage page switches between computers, and alerts from all of them arrive in one column.
A signed and notarised AigoPilot agent for Mac, with a one-step installer.
A separate installer for putting the agent on a second Windows PC.
Planned for a later version. Today the agent runs on Windows and macOS.
Planned for a later version. Today the studio itself runs on Windows 10 and 11.
Planned for a later version.
Yes. Put the AigoPilot agent on the Mac and pair it with six digits. Its Claude Code and Codex sessions then appear in the studio on your PC, and you start, prompt, answer and stop them from there.
Yes. Computers pair with a six-digit code using SPAKE2, and then talk over an encrypted Noise connection. A device that has not been paired gets no answer.
Not yet. The agent runs on Windows and macOS. A Linux agent is planned for a later version.
