What is Fleet
Fleet is the engine. It runs coding-agent sessions and keeps them running. You describe each
session as a Task and apply it with fleet apply. Fleet starts the
agent, sends it the brief, delivers your messages, records the result the agent reports, and
stops the session when you delete the Task.
Fleet works on its own. It is a command line and a manager process, with no interface. thurbox is one client of Fleet; a script, a cron job or another agent is another.
Sessions are Tasks #
A Task is a JSON object. It names:
- the harness: the coding agent, such as
claudeorcodex(Agents) - the host: the place the session runs,
localby default - the workspace: the repositories or directories the agent works in, as URLs
- the brief: what to do; a Task with no brief waits for you to type
fleet up keeps every Task moving. It is the manager: run it in a terminal or as a
service. Get started shows the commands.
Resources and controllers #
Fleet stores resources, and a controller for each kind moves them toward what their spec asks for. The plan lives in the store, not in a chat, so it outlives every session.
| Resource | What it is |
|---|---|
| Task | One agent session doing one brief |
| TaskConfig | Reusable defaults for Tasks: harness, place, environment |
| EnvProvider | A source of environment values for Tasks |
| ChangeRequest | One pull or merge request a Task's agent opened, mirrored from its forge |
| Conversation, Listener | A chat thread tied to a Task, and the chat account behind it |
Every resource and controller has its own page in Fleet's reference: resources and controllers.
Fleet runs each session at a place, through a runtime.
Next #
- Install Fleet, alone or with thurbox
- Get started: your first Task
- Fleet features