Skip to main content
Fleet consumes the upstream engine as a stock, checksum-pinned release tarball. Nothing upstream is vendored or patched in this repository.

​
The pin

PRIME_AGENT_RUNTIME.json at the repository root records:
packages/fleet-prime/package.json depends on the same tarball URLs, and web/server consumes the same pinned package. npm run check runs node scripts/check-prime-agent-runtime.mjs first, which fails if the manifest and dependencies drift apart.

​
Upgrading the pin

  1. Update PRIME_AGENT_RUNTIME.json and the matching dependency URLs in packages/fleet-prime/package.json.
  2. Reinstall: npm install at the root and pnpm --dir web install.
  3. Verify: node scripts/check-prime-agent-runtime.mjs, the web-server type checks, and the adapter parity tests.
  4. Review changes to the public runtime APIs consumed by web/server and to the daemon protocol before merging.
The daemon protocol is upstream-owned. When an upgrade changes the protocol or schema revision, review web/docs/architecture/fleet-adapter-contract-v1.md, update web/server, and run the daemon-runtime and bridge parity tests in the same PR.

​
Engine contributions

Engine features (providers, models, daemon protocol, CLI behavior) are developed in PrimeIntellect-ai/prime-agent. Contribute there first, then upgrade Fleet’s pin to a release that includes the change.

​
Cutting a Fleet release

A Fleet release ships the web product plus a packed CLI artifact:
  1. Upgrade the runtime pin if needed, then run npm install, pnpm --dir web install, and npm run check.
  2. Build and pack: npm run build && npm run build:web:release && npm run release:pack.
  3. Tag this repository. Fleet never publishes Prime Agent itself.
Last modified on August 30, 2026