Carrying a whole project to another computer

You can move a whole project to another computer of your studio: its files, the history of its AI sessions, and the programs it needs to run there. A typical case is a Unity project that grows too heavy for your main PC, and an idle laptop that can take it. After the carry you go on working on the project over there, with the same sessions, from the same studio.

Partly built. Carrying to another Windows PC is built and was used on a real project. A carry to or from a Mac has not been run from the studio. Not built yet: files the project keeps outside its own folder, a check that opens the project once on arrival, setting up the MCP servers its sessions used, and carrying back from the other side. What you changed here after a carry can be sent to the other copy.

Before you start

The other computer must be in the studio's list and on. If it is not, see Setting up a second Windows PC and Pairing two computers with six digits. An agent older than your studio says it cannot receive a project yet. Update it first, as described in Keeping AigoPilot up to date.

Select the project and click Carry to another computer, next to New session. The button shows only for a project that sits on the computer you are at, once another computer is in the list.

Read the plan

Under To which computer? nothing is chosen for you. A carry can be tens of gigabytes, so you pick the target yourself. The studio then reads the project and shows one list before anything is sent:

• Goes: how many files and how big. For a Unity project it also names the editor version the project was saved with.
• The largest parts, each with a tick. Untick one the other computer does not need, and it stays here.
• What stays behind because the project's tools make it again, such as Unity's Library folder, with its size. Untick one to send it too.
• Files that hold secrets of the project. They go, because the project does not run without them. Untick one to leave it here.
• Warnings: Unity has the project open, so what it has not saved is not in the files; or sessions are working in it now.

Under Where does it sit on the computer, the studio proposes a place and says why. The same path as here is the best answer, because every path written inside the project stays true. If the other computer has no drive of that letter, the path is taken, or the drive has no room, another place is proposed. A carry between Windows and a Mac cannot keep the path. It also shows the free room there, and says plainly when there is too little.

Send it

1. Check the plan and the place.
2. Click Carry to followed by the computer's name.
3. Watch the bar. It goes through Reading the project, Sending, Comparing both sides and Finishing, with the speed and the minutes left.

Files go in pieces, each checked by a hash. If the line drops, the carry waits and goes on from where it was when the line is back. Stop keeps what arrived, and the next carry continues from it. At the end both sides are compared file by file, and the studio says "All N files are the same on both sides". On the other computer, the agent's window shows a card A project is arriving with its own bar and a log you can open. The receiving side writes only under the place you agreed to, and the project on your PC is never changed.

The sessions go too

When the files are there, the window offers Send the sessions to the computer. Each conversation of Claude Code, Codex or Grok goes to the folder where that tool looks for it, so the same session continues over there. A file that is already there is not changed or overwritten. Pictures you gave to those conversations go too.

Both copies are marked. The session carries Continued at the computer on the copy it came from, and Came from the computer on the copy it arrived at. The arrival copy keeps its box closed until you have seen the size of the conversation and agreed with Continue it here, because the first message sent there reads the whole conversation again and that much comes out of your limit. A heavy conversation says so and suggests a fresh session.

On your PC the carried project is locked: it says it was carried and the work goes on there. The banner offers Open the copy there, Send what changed here, Work here anyway and Lock it again. Send what changed here lists new files, files changed only here, and files changed on both sides. Files changed on both sides are named and never overwritten, and a file replaced there is kept beside the project in an .aigopilot-replaced folder.

What the project needs over there

A Unity project must be opened with the editor version it was saved with. The studio reads that version and, on your click, installs it on the other computer with Unity's own command-line tool, after checking that the drive has room. Modules such as Android, with its SDK, NDK and Java, are listed and installed the same way. Google's license terms for Android are shown with their address and accepted only by your click. Node.js, Docker and the like are covered in Installing Claude Code and Codex on another computer.

If a program run as administrator wrote some files, Windows may call another account their owner, and Git then refuses to work. The studio notices, offers Make them mine, and does it after every carry. For the whole picture of working across machines, see Working on another computer, or the moving projects page.

Small tips

Questions