> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qredence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Fleet Prime Agent

> Fleet Prime Agent is a persistent local workspace for coding and research with AI: a multi-project web chat over the pinned Prime Agent engine.

Fleet Prime Agent combines a multi-project web workspace with the stock [Prime Agent](https://github.com/PrimeIntellect-ai/prime-agent) engine. The agent works through IPython, shell commands, file edits, plans, and subagents while every session persists on disk. Close the browser, come back later, and pick up where you left off.

Fleet installs as the `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-agent` from any project directory and get a browser UI for chat, project sessions, attachments, and workspace navigation, served on `127.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 `/refine` self-improvement workflow come from the pinned engine and work in the web workspace.

## Start here

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/fleet-prime-agent/quickstart">
    Install Fleet Prime Agent, add a provider, and run your first turn.
  </Card>

  <Card title="Install" icon="download" href="/fleet-prime-agent/install">
    What the installer does, requirements, and where files land.
  </Card>

  <Card title="Architecture" icon="diagram-project" href="/fleet-prime-agent/concepts/architecture">
    How the browser, web server, bridge, and pinned engine fit together.
  </Card>

  <Card title="HTTP API" icon="code" href="/fleet-prime-agent/reference/http-api">
    Every endpoint the web workspace exposes, with methods and purposes.
  </Card>
</CardGroup>

## How it relates to upstream Prime Agent

The engine version is pinned in `PRIME_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-prime-agent/guides/upgrading-the-runtime).

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](/fleet-prime-agent/guides/terminal) at any time.