Home

Fleet Prime overview

Fleet Prime is a local workspace for coding and research with AI. It combines a browser interface, a server-side adapter, a published launcher, and the stock Prime Agent runtime. Fleet owns the product and presentation layers; Prime Agent remains the execution engine. The repository README describes the same split in README.md.

What the repository contains

The workspace has five packages:

• web/app is the TanStack Start browser application. It owns the chat workspace, client state, routes, and browser-side HTTP/SSE consumption.
• web/server adapts the supported Prime Agent connection and daemon API to Fleet's handlers and browser-safe events.
• web/protocol defines shared request, response, event, presentation, and validation types.
• web/design contains Fleet's reusable UI, chat components, panels, OpenUI renderers, and design checks.
• packages/fleet-web is the public @qredence/fleet package. Its launcher starts the bundled web runtime or the terminal mode.

The workspace package list and dependency policy are in pnpm-workspace.yaml. The package manifests are in web/app/package.json, web/server/package.json, web/protocol/package.json, web/design/package.json, and packages/fleet-web/package.json.

Main user flow

Run fleet-agent from a project directory. The launcher starts the production Fleet web bundle, binds to loopback, and passes the project directory to the server through PRIME_AGENT_WORKSPACE_ROOT. The browser loads the single workspace route, creates or resumes a session, and sends turns through the typed chat API.

An active turn returns newline-delimited JSON. Session-level pushes use an SSE connection with bounded replay. The server maps daemon events into ChatStreamEvent values, and the browser reducer turns those frames into conversation state and panel state. The durable transport rules are in docs/reference/adapter-contract.md.

Product capabilities

• Multiple local projects with project-scoped session history.
• Streaming assistant turns, tool activity, queued messages, and cancellation.
• Plan-mode presentations and durable execution decisions.
• Provider credentials, custom providers, model discovery, and model settings.
• Workspace tree and file browsing.
• Managed IPython readiness reporting.
• Right-side resources, artifacts, REPL, session-insights, and subagent panels.
• OpenUI HTML artifacts validated before they are stored or rendered.
• A terminal entry point that delegates to the installed Prime Agent CLI.

The feature-oriented pages under features describe these capabilities without exposing upstream runtime objects to the browser.

Where to start

• Read architecture for ownership boundaries and data flow.
• Follow getting started to install or run the workspace.
• Use packages to find implementation ownership.
• Use the API reference for endpoint and stream details.
• Use contributing before changing code.

Source map

web/app/                 TanStack Start browser app and API route wrappers
web/server/              Prime Agent adapter, handlers, replay, sidecars
web/protocol/            Browser-safe wire types and Zod schemas
web/design/              Fleet presentation and reusable React components
packages/fleet-web/      Published launcher and bundled distribution
scripts/                 Checks, builds, packaging, installation, release
docs/                    Durable contracts and operation-specific guides

The root AGENTS.md is the repository-wide engineering contract. It states that code, tests, manifests, and executable checks are authoritative when documentation and implementation differ.

---

Generated by Factory