Use this file to discover all available pages before exploring further.
Fleet Pi loads configuration from .env at the repo root. apps/web/vite.config.ts is responsible for loading the file into the server-side routes; values are accessed through process.env at runtime.The canonical example lives in .env.example. This page is the authoritative reference for every variable Fleet Pi reads, grouped by concern.
Region for every Bedrock call. Models must be enabled in this region.
AWS_PROFILE
No
—
Use a named AWS profile from ~/.aws/credentials.
AWS_BEARER_TOKEN_BEDROCK
No
—
Set only if your Bedrock setup uses bearer-token authentication.
Fleet Pi uses the standard AWS credential chain — environment variables, profile, or IAM role. You can also provide AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY directly.
Pino log level. Logs are pretty-printed unless NODE_ENV=production.
NODE_ENV
No
—
Controls pretty-printing and a few Vite behaviors.
The logger lives in apps/web/src/lib/logger.ts. It includes PII redaction and emits a requestId correlation ID for every chat request, which lines up with bedrock-api circuit-breaker events for incident review.
Pi session files are persisted under .fleet/sessions/ inside the repo. The session manager rejects paths outside the repo-scoped directory via isUsableSessionFile, so a stale sessionFile in localStorage silently falls back to a fresh session — see runbooks for recovery.Canonical durable state lives under agent-workspace/. The workspace server reads canonical files directly and uses agent-workspace/indexes/ only as projection storage.