Skip to content
pilots
Dashboard

Install pilots in one command or a prompt

curl -fsSL https://pilots.run/install.sh | sh

What to run next

These four cover a first session. pilot --help has the rest, grouped by what you are trying to get done.

  1. pilot login

    Opens a browser, asks which team and what the key may do, and saves it to ~/.config/pilots/credentials, a file only your user can read. On a remote server with no browser it prints a code to enter instead, or pass --token with a key you already have.

  2. pilot deploy

    Run it inside a project. It takes a compose file, a Dockerfile, or neither, and a WebJs app needs no configuration at all. The last line it prints is the URL.

  3. pilot mcp install claude-code

    Writes the fleet into your coding agent's config, merged with what is already there. The agents page lists every harness it knows.

  4. pilot tui

    A terminal dashboard for your computers, services, logs and consoles, from the same binary. Leave it open.

Upgrading and removing it

Upgrading it

pilot upgrade

Downloads the newest release, checks it against the checksum file published beside it, and swaps it in with one rename, so an interrupted upgrade leaves the old binary working. pilot upgrade --check reports and changes nothing. Or ask your agent to upgrade pilot.

Removing it

rm ~/.local/bin/pilot

Your key is the one other file, ~/.config/pilots/credentials. Delete both and nothing of the CLI is left behind. Or ask your agent to remove pilot.