Skip to main content

​
Requirements

  • Node.js 22.8.0 or later (the installer refuses older versions)
  • npm 11.10 or later
  • Git
  • Python 3.10 or later for the managed IPython kernel

​
What the installer does

./fleet-prime.sh install runs install.sh, which:
  1. Verifies git, node, and npm are available and that Node meets the minimum version.
  2. Uses the current directory if it is already a Qredence/fleet-prime-agent checkout, or clones into it if it is empty. It refuses to overwrite a non-empty, unrelated directory.
  3. Installs root dependencies with npm ci. The root npm workspace contains the Fleet launcher and the pinned upstream runtime.
  4. Installs web dependencies with pnpm install --dir web --frozen-lockfile. If no compatible pnpm 11 is on your system, the installer runs pnpm 11.15.1 ephemerally through npm exec.
  5. Builds the Fleet packages and the production web bundle (scripts/build-web-release.mjs).
  6. Writes a fleet-agent launcher shim to ~/.local/bin (or a fallback directory if $HOME is not writable) that execs fleet-prime.sh in your checkout.
If fleet-agent does not resolve to the freshly installed shim, the installer prints the shim directory to add to your PATH.

​
Environment overrides

For testing or pinned source installs, install.sh reads:

​
Coexistence with an existing prime-agent install

Fleet installs as fleet-agent; it does not replace or shadow an existing prime-agent binary. If the installer detects prime-agent on your PATH, it leaves it untouched. Both commands share ~/.prime/agent/ settings, kernel venv, and logs.

​
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. See Configuration.

​
Updating

Pull the latest checkout and re-run the installer. It reuses the existing checkout, reinstalls dependencies, and rebuilds the production bundle:
Last modified on August 30, 2026