Move a project
with everything it needs.
Send a project to another of your computers with its AI sessions, leave out what tools rebuild anyway, and let AigoPilot install the Unity editor and tools it needs over there.
Moving a project by hand usually means copying gigabytes you did not need, forgetting the .env file, finding the wrong Unity version on the other side and losing the agent's whole history. AigoPilot moves the project as one piece. It was tried on a real Unity project of 25.9 GB and 54,599 files, which arrived complete.
Before the move you see what goes, what stays behind because tools rebuild it, and which secret files such as .env are included. Leave them out if you prefer. You also see the biggest folders, whether Unity has the project open, and any sessions working in it.
What stays behind is chosen by project type, not by .gitignore: Library, Temp and Logs for Unity, node_modules, Rust's target folder, bin and obj for .NET, Gradle's build folder and Python caches.
The project goes to the same full path on the other computer when it can, and otherwise to the same folders on a drive with enough room.
Files travel in 2 MB pieces, each checked with SHA-256, and the whole project is compared file by file at the end. A cut connection picks up where it stopped. The original copy is never touched.
The studio shows the speed, the time left and the current file. The receiving computer shows a bar and a timed log, and stays awake until the move is done.
Claude Code and Codex transcripts are added to the CLI's folders on the other computer without overwriting anything there. Session names, pasted pictures and archive marks come along, and usage is not counted twice. A moved Codex session has been continued on the receiving laptop. A moved Claude Code session has not yet been seen continued there.
The copy that stayed says where the project went, and the copy that arrived says where it came from. The old copy is locked until you choose to work there anyway.
AigoPilot reads the exact Unity version and revision the project was saved with, and installs that editor through Unity's own command-line tool after checking there is room on the disk.
Android build support, with its SDK, NDK and Java, can be installed as well. Google's licence is shown to you and accepted only when you click.
Node.js, Python, Rust, Git and Docker Desktop are recognised from the project's own files and installed with winget when you click. Docker Desktop is installed only after you accept its terms. winget has not yet been run for any of the five tools on a real machine. On a Mac the studio only names what is missing.
Moved files are made the working user's own, so Git does not refuse the repository on the new computer. Built, but the fix has not yet been run on a real carried project.
Carry a project back to where it came from, sending only the files that changed.
Paths the project uses outside its own folder, plus Unity saves and PlayerPrefs.
Open the project once in batch mode when it arrives, and read the import log for errors.
Set up the project's MCP servers and plugins on the other computer, without carrying their keys.
Before the move, ask the session that last worked on the project what it will need on the new computer.
Carry a project to or from a Mac, and install its tools there.
Pair the other computer with AigoPilot, pick the project and pick where it goes. AigoPilot leaves out Library, Temp and Logs, which Unity rebuilds, checks every file on arrival, and can install the exact Unity editor version the project was saved with.
No. Unity rebuilds it. AigoPilot leaves it behind, together with Temp and Logs, which makes the move much smaller.
The session files move with the project and are added to the CLI's folders there. A moved Codex session has been continued on the receiving computer. Continuing a moved Claude Code session has not been tried yet.
