Fleet RLM
Fleet RLM is a terminal-based assistant for work that needs reasoning, Python, and files. Ask a question, watch its work stream into the terminal, and return to a saved Session later. Fleet uses DSPy for the RLM reasoning loop, Daytona for isolated execution, and FastAPI for its backend.
What you can do
- See the work as it happens. The terminal shows reasoning, generated Python, tool activity, and results in one timeline.
- Continue a Session. With a configured database, committed conversation history survives a restart.
- Work with files. Attach local files to a Turn, inspect workspace files, and download committed Artifacts.
- Choose how much delegation to use. The default profile supports DSPy's native semantic calls. An optional profile enables bounded, isolated child RLMs for independent investigations.
Run a live local Session
You need Python 3.11–3.13, uv, Node 22.19+, pnpm, a Daytona account, and a key for the model provider in the shipped profile. The repository includes a local SQLite configuration; a separate PostgreSQL setup is not needed to try Fleet.
1. Install
git clone https://github.com/Qredence/fleet-rlm.git
cd fleet-rlm
uv sync --dev
pnpm --dir tools/fleet-tui install --frozen-lockfile
2. Add credentials
cp .env.example .env
Open .env and fill in ALIBABA_API_KEY, FLEET_DAYTONA_API_KEY, and
FLEET_DAYTONA_ORG_ID. The example already supplies the local SQLite URL and
the DashScope base URL used by the default daytona-native profile. Keep
secrets out of Git. For another model provider or deployment profile, use the
configuration guide and
profile matrix.
3. Initialize and start
uv run python scripts/db_init.py
uv run fleet cli
Fleet does not migrate the database on startup. fleet cli starts the backend
and opens the terminal client. Try a prompt such as “Use Python to calculate
the first 20 Fibonacci numbers and explain the result.” /help shows the
available commands. Fleet prints the Session ID so you can return later:
uv run fleet cli -- --session <session-uuid>
The first live Turn uses the configured model provider and Daytona Sandbox.
uv run fleet doctor daytona is an optional, disposable connectivity and
mount probe when setup fails. See the CLI guide for
diagnostics and launch options.
In the terminal
| Command | Use it to |
|---|---|
/help |
Find commands and keyboard shortcuts. |
/attach <path> |
Add a local file to the next Turn. |
/files |
Browse the Workspace files/ area. |
/artifacts |
List Artifacts from the conversation. |
/sessions |
Switch between saved Sessions. |
/profiles |
Select a runtime profile for the next restart. |
The terminal guide covers file downloads, themes, Skills, cancellation, and other controls.
How it works
Terminal client → FastAPI/SSE backend → DSPy RLM → Daytona Sandbox
↘ durable Sessions and committed results
The backend prepares each request, runs model-authored Python in Daytona, and
streams progress to the terminal. It commits an answer and any Artifacts only
after the Run settles. The default daytona-native profile keeps full child
RLMs disabled; daytona-recursive is an explicit opt-in. Runtime policy lives
in config/fleet.toml, and profile changes take effect after a restart.
Fleet also exposes the backend without the terminal through uv run fleet web
or uv run fleet-rlm serve-api --port 8000. The API binds to loopback by
default and has no caller authentication. See the HTTP API reference
and generated OpenAPI contract.
Learn more
- Documentation home — guides and reference pages.
- Architecture — component ownership and trust boundaries.
- Contributing — development setup, tests, and change workflow.
License
MIT — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for fleet-rlm 0.7.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fleet_rlm-0.7.10.tar.gz | 461.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fleet_rlm-0.7.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 998.8 kB
Release files / fleet_rlm-0.7.10.tar.gz
| Download URL | fleet_rlm-0.7.10.tar.gz |
|---|---|
| Size | 461.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
74392d801adf122710bf4af2e27c14a4e0d3cb2b7bdd4ad80b080b8e0f28c606
|
|
BLAKE2b-256 checksum How to use checksums |
ff14a584300eb84b0c34a212dceea8c99737e9c1152f6069cb6c8c18248cd977
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency logRelease files / fleet_rlm-0.7.10-py3-none-any.whl
| Download URL | fleet_rlm-0.7.10-py3-none-any.whl |
|---|---|
| Size | 537.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e948f7f6f9b744a5120d7c0a1080d65f190ac67fa37e43567b3dceab8e371a59
|
|
BLAKE2b-256 checksum How to use checksums |
649a1d0f79d3944056cc86fd6d10f69dc6b2aa12fead949f7cc7fa2a454c20d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency log
