fleet-agent command. It does not fork or patch the engine: the upstream prime-agent runtime is consumed as a checksum-pinned release tarball, and the web stack in this repository is the interface on top of it.
What it does
- Local web workspace. Run
fleet-agentfrom any project directory and get a browser UI for chat, project sessions, attachments, and workspace navigation, served on127.0.0.1. - Streaming tool cards. Agent work streams as dedicated cards for IPython, shell commands, edits, plans, subagents, and interactive questions.
- Persistent sessions. Every session is backed by the engine’s persistent IPython kernel and a transcript on disk under
~/.prime/agent/, so state survives page reloads and restarts. - Engine features included. Recursive subagents, executable skills, slash commands, and the
/refineself-improvement workflow come from the pinned engine and work in the web workspace.
Start here
Quickstart
Install Fleet Prime Agent, add a provider, and run your first turn.
Install
What the installer does, requirements, and where files land.
Architecture
How the browser, web server, bridge, and pinned engine fit together.
HTTP API
Every endpoint the web workspace exposes, with methods and purposes.
How it relates to upstream Prime Agent
The engine version is pinned inPRIME_AGENT_RUNTIME.json (currently prime-agent 0.8.1) with a SHA-256 checksum. Engine behavior, providers, models, and the daemon protocol are developed in PrimeIntellect-ai/prime-agent, not in this repository. Fleet upgrades the pin explicitly and verifies adapter compatibility on every upgrade. See Runtime pin and releases.
Fleet coexists with an existing prime-agent install. Both commands share ~/.prime/agent/ settings, kernel venv, and logs, so you can switch between the web workspace and the terminal interface at any time.