Skip to main content
The terminal client is a full-screen Textual app in the fleet_rlm package. It talks to the server over the public HTTP API. When standard input isn’t a terminal, it falls back to plain Rich output.

Start the terminal

fleet cli starts the API server and local MLflow, waits for readiness, and opens the client. To resume a Session, pass the same --session ID. To connect to a server that’s already running, pass --url. See the CLI reference for every flag.

Setup checklist

Before it starts its own server, fleet cli checks four sections: Models, Database, MLflow, and Daytona. When every check passes without warnings, the client opens directly. Otherwise Fleet opens the setup checklist. In the checklist, you can:
  • Fill in missing settings and save them to .env with Save .env. Secret fields stay masked. Leave a configured secret blank to keep it.
  • Run Verify for every section, or verify one section at a time.
  • Send one small test request to the Root model. The provider may charge for it.
  • Find or create a Daytona workspace Volume, and build or activate the packaged Daytona snapshot. Creating a Volume and building or activating the snapshot change your Daytona organization, so Fleet asks you to confirm first.
  • Choose Start / Restart to start Fleet with the saved settings.
Type /setup in the client to reopen the checklist. Fleet restarts the services it owns after you apply changes, then reopens the same Session. When the client is connected to a server that Fleet didn’t start, /setup prints Setup is managed by the server operator. The setup endpoints exist only on that local operator connection, not on the public HTTP API.

Use the terminal in a browser

fleet web serves the same client in a browser at http://127.0.0.1:8080. Each browser client gets its own Session unless you pass --session. See fleet web for flags and for exposing it beyond your machine.

Run a task

Type a task without a leading slash and press Enter. The client renders live server events: routing, tool calls, Python code and output, child sandboxes, budgets, the final answer, errors, and cancellation.
  • Task REPL cells expand while they run and collapse to a one-line summary when they finish cleanly. Failed cells stay expanded.
  • Routing panels summarize the decision. They don’t show private model chain-of-thought.
  • After the server commits the Turn, the Turn card shows Turn persisted to Session history. When tracing is on, the card also shows the MLflow trace ID.
  • While the Turn runs, the activity line shows the advisory status, such as waiting_on_host or stalled, with any progress scope and checkpoint. These labels never stop the Turn. See Status and progress events.
  • When the Turn ends, the Turn card shows the duration the server recorded.
  • An incomplete stream is labeled unknown, not persisted. A lost connection doesn’t prove the Turn rolled back, so check /history or /turn before you retry.

Keyboard shortcuts

You can also click a ▸ or ▾ row to expand or collapse it.

Mention files with @

Type @ in a task to get suggestions for local files and folders, and for workspace files the client has already seen. A bare name also matches files in nested folders. Quote paths that contain spaces, for example @"my notes.txt". Browsing suggestions never uploads anything. When you submit the task, the client uploads each mentioned local file or folder to a unique path under files/ in the workspace and rewrites the mention to that path. Mentions of existing workspace files are sent unchanged.
  • Folder uploads keep their structure. They skip hidden files, symlinks, and files that Git ignores. In a Git working tree, Git must be installed.
  • Folder uploads are limited to 1,000 files and 100 MB per submission.
  • A path that starts with ./, ../, /, or ~/ must exist, or the client refuses to submit.

Slash commands

Type /help for the live list. It shows each command with its arguments. /exit or /quit closes the client.

Session and models

Model and mode selections apply at the next Turn and persist with the Session. A busy Session rejects changes instead of changing a running Turn. /timeout applies only to this client. The client sends it as timeout_seconds with each Turn and doesn’t save it with the Session. Daytona’s own sandbox lifetime bounds still apply when the Fleet deadline is off. See Turn deadlines.

Workspace and context

Skills and memory

Evaluation and traces

Last modified on November 8, 2026