Qredence Documentation

fleet-rlm is distributed as a source repository. Install it with uv and, if you plan to use the supervised fleet cli command, install the pi-tui workspace with pnpm.

Prerequisites

Python 3.13
uv package manager
Daytona API key for Sandbox execution
Postgres (FLEET_DATABASE_URL) for durable deployments; local SQLite works for development
Node 22.19+ and pnpm if you want fleet cli to launch the pi-tui terminal client

1. Clone and sync

git clone https://github.com/qredence/fleet-rlm.git
cd fleet-rlm
uv sync --all-extras --dev

--all-extras --dev installs the runtime, benchmarks, and test extras. Verify the CLI entrypoints:

uv run fleet --help
uv run fleet-rlm --help

2. Select a runtime profile

Non-secret policy lives in config/fleet.toml. Set [config] default_profile to one of the shipped profiles (daytona, daytona-recursive, daytona-managed, daytona-bench, daytona-bench-40) before starting the backend. The committed default is daytona-recursive. Only the environment variables named by the selected profile are read. Unknown keys, missing profiles, invalid variable references, and absent TOML fail startup. See the configuration reference for the full env matrix.

3. Configure credentials

Copy the shipped template and fill only the variables named by the selected profile:

cp .env.example .env

At minimum for the interactive profiles:

FLEET_DAYTONA_API_KEY=...
FLEET_DATABASE_URL=postgresql+asyncpg://user:pass@host/db
FLEET_OPENCODE_GO_API_KEY=...
FLEET_OPENCODE_GO_BASE_URL=https://<gateway>/v1

Process exports override .env for those named values.

4. Provision the Daytona base snapshot

Fleet child sandboxes bootstrap from a reusable base snapshot. Build or refresh it once:

make daytona-snapshot-check
# or, to rebuild explicitly:
uv run fleet-rlm daytona-snapshot --refresh

5. Bring the database to the Alembic head

Runtime startup never applies migrations. Initialize the configured database explicitly:

uv run python scripts/db_init.py
uv run alembic upgrade head
uv run alembic check

fleet cli verifies the head before starting the backend and refuses to proceed otherwise. Recover from a mismatch by re-running scripts/db_init.py and retrying.

6. (Optional) Install pi-tui

fleet cli supervises the backend and runs the pi-tui terminal client in the foreground. Install its workspace once:

cd tools/fleet-tui
pnpm install --frozen-lockfile
cd ../..

You can also connect a standalone pi-tui to an already-running backend:

pnpm --dir tools/fleet-tui start -- --session <session-uuid>

Set FLEET_API_URL to point pi-tui at a non-default host, for example http://127.0.0.1:9000.

7. Verify

Run the Daytona doctor to validate settings, database head, provider auth, Volume visibility, mount scoping, and interpreter execution:

uv run fleet doctor daytona

Then start Fleet:

uv run fleet cli
# or, backend only:
uv run fleet-rlm serve-api --port 8000

Common Makefile targets

Target	What it does
`make check`	Run the standard quality gate.
`make check-security`	Run security scanners.
`make build-release`	Build the release artifacts.
`make check-release`	Run the release-readiness gate.
`make api-sync`	Regenerate `openapi.yaml` and `tools/fleet-tui/src/generated/openapi.ts`.
`make api-check`	Verify both regenerated artifacts match the source.
`make daytona-snapshot-check`	Verify the required Daytona base snapshot exists.

Next steps

Quickstart

Stream your first Turn.

Configuration reference

config/fleet.toml profiles and the full env matrix.

CLI reference

fleet cli, fleet doctor daytona, fleet-rlm serve-api.

Deployment

Run the backend under process supervision.

Fleet-RLM

Fleet Pi

GEPA Omni

Qredence Skills

Fleet Reasoner

Qredence Plugins

Install fleet-rlm

Prerequisites

1. Clone and sync

2. Select a runtime profile

3. Configure credentials

4. Provision the Daytona base snapshot

5. Bring the database to the Alembic head

6. (Optional) Install pi-tui

7. Verify

Common Makefile targets

Next steps

Quickstart

Configuration reference

CLI reference

Deployment

​Prerequisites

​1. Clone and sync

​2. Select a runtime profile

​3. Configure credentials

​4. Provision the Daytona base snapshot

​5. Bring the database to the Alembic head

​6. (Optional) Install pi-tui

​7. Verify

​Common Makefile targets

​Next steps

Quickstart

Configuration reference

CLI reference

Deployment

Prerequisites

1. Clone and sync

2. Select a runtime profile

3. Configure credentials

4. Provision the Daytona base snapshot

5. Bring the database to the Alembic head

6. (Optional) Install pi-tui

7. Verify

Common Makefile targets

Next steps