Skip to main content
fleet-rlm exposes two command entrypoints:
  • fleet — user-facing launcher for supervised backend + pi-tui, backend-only, and diagnostics.
  • fleet-rlm — Typer command group with subcommands for server modes and Daytona snapshot management.
All launchers default to binding 127.0.0.1 and reject non-loopback hosts (0.0.0.0, LAN addresses, hostnames other than localhost) unless --allow-non-loopback-bind is supplied deliberately. Before starting a Daytona backend, set [config] default_profile in config/fleet.toml to one of daytona, daytona-recursive, daytona-managed, daytona-bench, or daytona-bench-40. The pi-tui /profiles command edits that key interactively for the next restart. fleet cli accepts only profiles whose runtime environment is daytona and fails before database preflight, MLflow startup, or backend spawning on any other selection.

​
fleet cli

Supervised backend plus pi-tui in the foreground.
Behavior:
  • Starts the backend in its own process group and waits up to 90 seconds for Daytona readiness.
  • Runs pi-tui in the foreground with native scrollback. Ctrl+C reaches pi-tui.
  • Owned-process shutdown escalates from termination to forced stop after five seconds.
  • Requires Node 22.19+, pnpm, an installed pi-tui workspace (tools/fleet-tui/), and an unused port.
  • Verifies the configured database is at the canonical Alembic head. Recover with uv run python scripts/db_init.py and retry.
For the interactive daytona and daytona-recursive profiles, fleet cli also starts the installed MLflow server on 127.0.0.1:5001 with one worker, SQLite metadata under .fleet_rlm/mlflow/mlflow.db, and artifacts under .fleet_rlm/mlflow/artifacts. It reuses an already-running server only when GET /version matches the installed MLflow version, and never stops a reused process. Benchmark profiles disable tracing; standalone backend commands require the configured tracking server to be started separately. Backend and owned MLflow output stream to timestamped files under .fleet_rlm/logs/; latest.log and mlflow-latest.log point to the active logs. Forward terminal options after --:
Artifact mode downloads content, checks length and SHA-256, fsyncs a temporary file, and atomically renames it. It does not start the interactive screen.

​
fleet web

Backend-only launcher. Uses the profile selected by [config] default_profile.
Does not launch pi-tui. There is no Fleet-shipped web UI; connect a client to the SSE surface directly, or run pi-tui standalone against the API:
Set FLEET_API_URL to point standalone pi-tui at a non-default host.

​
fleet doctor daytona

Opt-in disposable probe that validates required settings, database connectivity, Alembic head, provider authentication, Volume visibility, scoped mounting, and interpreter execution.
The probe creates one uniquely labelled disposable Sandbox, deletes it in finally, creates no Fleet domain rows, and prints only bounded categories and corrective actions. Run it before diagnosing a real Turn.

​
fleet-rlm serve-api

Same backend as fleet web, exposed as a Typer subcommand.
Uses the profile selected by [config] default_profile. Does not launch pi-tui and does not manage MLflow.

​
fleet-rlm daytona-snapshot

Create or refresh the reusable Daytona base snapshot child sandboxes bootstrap from.

​
See also

Last modified on August 13, 2026