Installing AigoPilot on Linux, and the agent on a server

AigoPilot runs on Linux as the full studio, with the same window, sessions and plugins as on Windows. The same program is also the agent, so a Linux server without a desktop can do the work while you drive it from a studio on another computer. This page covers both: installing on a desktop, and setting up a server.

New. The Linux version came out in October 2026. It is made for x86_64 computers only for now, and it needs glibc 2.35 or newer: Ubuntu 22.04 or newer, Debian 12, Fedora, Arch, Linux Mint 21 or newer, RHEL or Rocky Linux 9, and others of the same age.

Next to the official Linux apps: Claude Code on Linux, Codex on Linux.

Choose a package

There are two downloads. They hold the same program.

• Download the AppImage (AigoPilot-<version>-linux-x86_64.AppImage). One file that runs on any distribution with a desktop. It keeps itself up to date.
• Download the .deb (AigoPilot-<version>-linux-amd64.deb). For Ubuntu 22.04 or newer and Debian 12. Your system's package manager installs it and keeps track of it.

Both downloads are free. The studio works with your AigoPilot account and its plan, as on Windows; see plans and your account. An agent works once a studio with a plan pairs with it.

Linux has no warning screen like Windows SmartScreen, and we do not sign the packages with a paid certificate there. The program checks its own signature when it starts, and every update is checked against our key before it is used.

Install the AppImage

1. Download the file.
2. Make it runnable. In a terminal: chmod +x AigoPilot-*.AppImage. Or right-click the file, open Properties, and tick Allow executing file as program.
3. Start it with a double click, or with ./AigoPilot-*.AppImage in the terminal. The studio opens, and its first-run setup starts by itself.

On a desktop nothing else is needed. You do not need libfuse2, which older AppImages asked for. Keep the file in a folder that stays, such as ~/Applications, because the studio starts itself from that file when it starts with the computer.

Updates. The AppImage looks for a newer build on aigopilot.com about once a day. It downloads it, checks it, and puts it in place of its own file. Once no session is working, it starts again as the new version.

Install the .deb

Open a terminal in the folder of the download and type:

sudo apt install ./AigoPilot-*.deb

Type the ./ at the start: it tells apt to use the file and not to look for a package of that name online. apt also installs what the program needs. AigoPilot then shows up in the list of applications. The program itself is /usr/bin/aigopilot.

Updates. The studio tells you when a newer build exists, but it never changes a package of the system by itself. Download the new .deb and install it with the same line. To remove AigoPilot: sudo apt remove aigo-pilot (the name of the package has a hyphen).

Your data, meaning the index of your sessions and your settings, lives in ~/.local/share/com.aigopilot.studio with either package. Removing the program leaves it alone.

A server without a desktop

On a server you reach over SSH, run the program as an agent. It has no window there. You type its commands, and a studio on another computer (Windows, Mac or Linux) does the rest.

With the .deb, install it as above. It brings every library the program needs.

With the AppImage, install the desktop libraries first, because the program needs them even without a window:

# Ubuntu, Debian
sudo apt install libasound2 libfontconfig1 libwayland-client0 libx11-6 libx11-xcb1 libfribidi0 libfreetype6 libxcb1 libexpat1 libharfbuzz0b libgbm1 libdrm2 libgl1 libegl1

# Fedora
sudo dnf install alsa-lib fontconfig libwayland-client libX11 libX11-xcb fribidi freetype libxcb expat harfbuzz mesa-libgbm libdrm libglvnd-glx libglvnd-egl

On a computer without FUSE (a container, or some virtual servers), the AppImage stops with a message about --appimage-extract. Start it once like this, and it keeps starting that way by itself, also with the computer:

./AigoPilot-*.AppImage --appimage-extract-and-run --agent

Then use these commands. With the AppImage, type the path of the file in place of aigopilot.

• aigopilot --agent starts the agent. It keeps running after you close the terminal and the SSH connection. Run it again and it only says how it stands.
• aigopilot --agent --pair shows six digits for a studio on the same network, the addresses and port, and a code for a studio on another network. It waits and says who paired.
• aigopilot --agent --state shows the name, the build, where the agent can be reached, and the studios paired with it.
• aigopilot --agent --name "Build server" sets the name the studio shows.
• aigopilot --agent --autostart boot starts the agent with the computer, before anybody signs in. signin starts it at your first sign-in, and off stops both. It uses a systemd service of your own user and needs no administrator. If your system lets only an administrator keep a user's services running, the command prints the one line to type.
• aigopilot --agent --stop stops the agent. It closes its sessions first.

To pair, open Settings, then Computers in your studio, and under Add a computer type the six digits. From another network, type the code in place of the address. The whole exchange is in pairing two computers with six digits. The agent updates itself from aigopilot.com, as the AppImage does. With the .deb, install the newer package by hand.

Sign in to Claude Code and Codex without a browser

Once the server is paired, its row in the Computers window lists Claude Code, Codex and Grok. The studio installs a missing one with its maker's own installer, into your user folder on the server; see installing the tools on another computer.

A server has no browser, so the tools sign in with a code. Click Sign in in the tool's row.

• Codex (and Grok): the row shows a code and an address. Click Open the sign-in page, which opens the address in the browser of the computer you sit at. Sign in there and type the code the row shows. The row turns to a tick when it is done.
• Claude Code: the row shows a long address. Click Open the sign-in page and sign in. At the end the page shows a code. Copy it into the box The code the sign-in page shows in the row, and click Send the code.

A code lasts about 15 minutes. If it runs out, click Sign in again for a new one. The studio never sees your password: you type it on the maker's own page. The box for Claude Code's code needs a studio from 22 October 2026 or newer. An older studio shows the address on one line, which you can copy with a triple click.

On a Linux computer with a desktop, the sign-in opens in a terminal window on that computer instead, for whoever sits at it.

Questions