Fleet features

What Fleet does, with or without thurbox. For what the interface adds, see thurbox features.

Sessions as Tasks #

Every session is a Fleet Task. Fleet starts it, sends its brief once, keeps it running and reports its status. The runtime keeps each session's terminal in a multiplexer window (tmux, or psmux on native Windows), so a session survives its client quitting or crashing, and several clients see the same sessions. After a reboot, the next fleet up brings the sessions of unfinished Tasks back.

fleet delete task <name> stops the agent and releases the session. There is no undo.

Agents are harness profiles #

A Task names its agent as a harness. Fleet's harness profile for it owns the command, its arguments, how to resume it and how it reports its status. Fleet bundles nine, and a new agent is one more profile file. See Agents.

Worktrees made by the runtime #

Each Task works in a workspace its runtime makes at its place: a git worktree of your checkout on a branch of its own, or a directory as it is. Deleting the Task keeps the branch. Workspaces covers where it lives, release and preserved work, and several repositories in one Task.

Places and runtimes #

A runtime is a program Fleet runs to start and stop processes; runtime-mux is the one Fleet ships, and any program that speaks the runtime protocol can be another (fleet runtime check -- <program> tests one). A place is where a runtime runs a session, named <runtime>/<place>; local is the Fleet's own machine. A Task names its place in host. See Places and runtimes.

Messages between agents #

fleet send <task> <text> queues a message for a session's agent, and Fleet delivers it on its next pass, once the session is ready. One agent hands another a payload this way instead of scraping its terminal. The Task's status.inbox records what was queued and delivered, and --answers <id> marks a message as the answer to a question the Task declared. A worker reports its outcome with fleet result.

Scheduled Tasks #

A CronTask creates a Task at each time of a cron schedule, from a Task template: a nightly review, a weekly dependency update, a check every hour. Its controller keeps a short history and, by default, skips a time while the previous Task still runs.

Headless CLI #

fleet drives every session from a script. thurbox reads the same Fleet, so a change made either way shows in the other.

To Run
List sessionsfleet list task
Read onefleet get task <name> (JSON)
See why it is where it isfleet status task <name> --json
Create onefleet apply --create-only -f <task.json>
Send its agent a messagefleet send <task> <text>
Label itfleet label task <task> <key>=<value>
Print the command that opens its terminalfleet attach <task>
Follow changesfleet watch --json
Delete itfleet delete task <name>

Fleet also follows the pull requests a worker opens and can tie Tasks to chat threads; see the Forge controller and the Gateway controller. It follows changes on GitHub, GitLab, Azure DevOps and Bitbucket Cloud; see the supported forges. Orchestration patterns are in Orchestration.