Skip to content

Releases: pilotsrun/pilots

Release list

pilot v0.2.0

Choose a tag to compare

@github-actions github-actions released this 19 Sep 17:18
cfe7fcf

The first published release of pilot, the command line and terminal dashboard for Pilots, as one static Go binary. It succeeds the TypeScript CLI's 0.1 line, which was published as @pilots/cli and is now deprecated.

Added

  • Two ways to install. curl -fsSL https://pilots.run/install.sh | sh puts the binary in ~/.local/bin with no sudo. npm install -g pilots carries the binary for every supported system and runs no install script, and npx pilots deploy runs it with nothing installed. Both are on the install page.

  • The installer verifies, or installs nothing. The download is checked against the checksums.txt published beside it. A checksum that cannot be fetched, a missing line, a mismatch, or a machine with no sha256sum or shasum each stop the install before anything lands on your PATH.

  • pilot upgrade verifies too. The new binary is checked against the same file before it replaces the running one with a single rename, so an interrupted or tampered download leaves the old binary working. pilot upgrade --check only reports.

    A binary that npm or Homebrew installed is left to its manager: pilot upgrade and --check both print the command that upgrades it there.

  • One command line for sandboxes and services. pilot deploy takes a directory to a URL from a compose file, a Dockerfile, or neither. pilot machines, console, exec, file and proxy drive a sandbox, pilot promote turns one into a service without changing its URL, and services, logs, domains, secrets and volumes run it in production.

  • pilot tui. The fleet as a dashboard you leave open, from the same binary.

  • pilot mcp install <harness> connects Claude Code, Codex, Cursor and the other agents listed on the agents page to the fleet's hosted MCP server.

Limits

  • Linux and macOS, on x64 and arm64. There is no Windows build. WSL is Linux, so both installs work there unchanged, and on Windows itself the npm package says so and points at WSL.
  • A checksum proves the file you received is the file the release published. It is not a signature. The npm package carries a provenance record that ties it to the commit and the workflow run that built it.

Install, or upgrade an install the script made:

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

From npm: npm install -g pilots@latest. Every way in is on https://pilots.run/install.