Updates: the studio, the agents and the AI tools

Three kinds of program need to stay current when you use AigoPilot: the studio on your Windows computer, the AigoPilot agent on any other computer you have paired, and the AI tools themselves, meaning Claude Code, Codex and Grok. They update in three different ways, and the studio checks that they still fit each other.

Partly built. The agents and the AI tools update by themselves. The studio itself does not yet: a new studio means running a newer installer over the old one.

The studio

Run the newer installer. It finds the copy that is there, offers to remove it first or install over it, and keeps your data either way. Details, and the warning about closing a running studio, are in installing AigoPilot. Close the studio's work first: closing it stops the engine, and a session that is working stops with it.

Settings, then Computers, shows the build of the studio you run, as This studio: version 0.1.0, built followed by a date and time. Two builds with the same version number are told apart by that time. Quote it when you report a problem.

The agent on another computer

The agent is the same program as the studio, started in its own mode, so a Mac or a second Windows computer can run sessions for you. It looks for a newer build on aigopilot.com once a day, and at once when you press Check for updates in its own window. A newer build is downloaded, checked, and put in place as soon as no session works on that computer. Then the agent starts again as the new build.

What the agent trusts on the site is a list that carries our signature. Each file in it has a size and a checksum, and a file that does not match is thrown away. The agent only ever moves forward: it takes a build made after the one it runs, never an older one. On a Mac the program must also be signed by the company and approved by Apple before it is put in place.

A Windows agent can also be updated from the studio. In Computers, a computer whose build differs from the studio shows Update the agent, and the studio sends its own build over the paired line. The update waits, and says why, while a session works there, while a session has left a program open (Unity's editor, for example, since the restart would close it), or while a project is arriving. A Mac agent has no such button, and its card says it is not updated from there. It updates from the site by itself.

Claude Code, Codex and Grok

Once a day, ten minutes after the engine starts and then every 24 hours, AigoPilot runs each tool's own update. It does this only while no session works on that computer. If something is running, it tries again an hour later. This applies on every computer with an engine, so a laptop that is paired gets its tools updated too. The tools' versions are the ones the tools report, and the setup page lists them.

When versions do not fit

The studio and an engine on another computer tell each other their build. When they cannot talk, you see one of these:

• "This studio is older than the engine it reached. Update the studio."
• "The engine the studio reached is old and has to be updated."
• "The agent on that computer is older than this studio and cannot receive a project yet. Put the new files of the agent there and open it again."

An agent from before updates could be sent from the studio shows An older agent that does not name its build. It has to be replaced by hand once. After that it updates itself. See also a computer says it is out of reach.

The backup before a change to your data

Your sessions are indexed in one file in the data folder, %APPDATA%\com.aigopilot.studio. When a new studio changes how that file is laid out, the studio copies the file into a backups folder beside it first, named aigopilot-v<number>-<date>-<time>.db. If you run an older studio on a data file made by a newer one, it leaves the file untouched and says so. The index can be rebuilt from the tools' own transcripts.

Questions