Requirements
- macOS or Linux on arm64 or x64. Windows is not supported.
- Node.js 22.12.0 or later
- Python 3.10 or later for the managed IPython kernel
Install from npm
The published npm package is the supported way to install Fleet:@qredence/fleet package installs two commands, fleet-agent and its alias fleet-prime. It bundles the production web workspace, so you do not need a repository checkout.
Run it from the project directory you want the agent to work in:
First launch
The first time you runfleet-agent, Fleet downloads the pinned Prime Agent Rust runtime for your platform (darwin-arm64, darwin-x64, linux-arm64, or linux-x64). Fleet checks the SHA-256 of the downloaded archive and of the extracted prime-agent executable against the pin. If either checksum does not match, Fleet refuses to install the runtime.
Fleet caches the verified binary, together with the prime-agent-runtime directory the kernel starts from, under ~/.prime/fleet/runtimes/<version>/<platform>/. Later launches reuse the cache without a download. If an earlier Fleet release left only the binary, Fleet downloads and repairs the runtime on the next start. The first launch needs network access to the release host.
To run a different native Prime Agent binary instead, set FLEET_PRIME_AGENT_BIN to its path. See Configuration.
Updating
Reinstall the package to move to the latest release:~/.prime/fleet/runtimes/. When the daemon protocol is unchanged, as in the move to 0.10.2, your existing sessions keep working.
Coexistence with an existing prime-agent install
Fleet installs asfleet-agent; it does not replace or shadow an existing prime-agent binary. Both commands share ~/.prime/agent/ settings, kernel venv, and logs.
Fleet’s cached runtime is independent of any global prime-agent CLI. Installing, upgrading, or removing the CLI does not change Fleet’s pinned version or its cache.
Fleet runs its own daemon on $TMPDIR/prime-agent-<uid>/daemon.sock. Before starting a daemon, Fleet probes that socket and reuses a running Rust daemon with a compatible protocol. Fleet refuses to attach to a TypeScript prime-agent daemon on that socket, even if its protocol matches. Stop that daemon before you start Fleet.
macOS limits Unix socket paths to 103 bytes, so a deeply nested TMPDIR can stop the daemon from binding. Keep TMPDIR short when you run Fleet.
Where things live
Session and engine state is owned by the pinned runtime under~/.prime/agent/: provider credentials and settings, session transcripts, logs, and the managed Python environment for the IPython kernel. Fleet stores its downloaded runtime binaries under ~/.prime/fleet/runtimes/. See Configuration.
Install from source (contributors)
Use the source installer only when you want to develop Fleet or validate a repository checkout. It needs Git, Node.js 22.12.0 or later, and npm../fleet-prime.sh install runs the same installer. install.sh:
- Verifies
git,node, andnpmare available and that Node meets the minimum version. - Uses the current directory if it is already a
Qredence/fleet-prime-agentcheckout, or clones into it if it is empty. It refuses to overwrite a non-empty, unrelated directory. - Installs workspace dependencies with
pnpm install --frozen-lockfile. If no compatible pnpm 11 is on your system, the installer runs pnpm 11.15.1 ephemerally throughnpm exec. - Builds the production web bundle with
pnpm run build. - Writes a
fleet-agentlauncher shim to~/.local/bin(or a fallback directory if$HOMEis not writable) that execsfleet-prime.shin your checkout. An existingfleet-agentfile or symlink at that path is replaced, not written through.
fleet-agent does not resolve to the freshly installed shim, the installer prints the shim directory to add to your PATH. If it detects prime-agent on your PATH, it leaves it untouched.
For testing or pinned source installs, install.sh reads:
To update a source install, pull the latest checkout and re-run the installer: