Skip to main content
Auto-generated overview of the monorepo workspace. Start with the Introduction and Quickstart if you are new to Fleet Pi.

Workspace layout

Key dependencies

Data flow

  1. The browser sends a user message to /api/chat via NDJSON stream.
  2. The server route sanitizes input (PII), logs with correlation IDs, and creates or resumes a Pi session.
  3. The Pi server module invokes Amazon Bedrock through a circuit breaker.
  4. Streaming events (start, delta, tool, done, error) flow back to the client.
  5. The client hydrates messages from the Pi session file on reload and opens supporting resources/workspace panels on demand.
  6. Supporting endpoints expose models, resources, workspace files, sessions, and health checks.
  7. Durable agent context lives in agent-workspace/, including project memory, plans, artifacts, and workspace-installed Pi resources.
Last modified on June 9, 2026