Agent groups (Cohorts) · Rune Box docs

runeward cohort talks to a running runeward serve.

Command	What it does
`runeward cohort up [charter]`	Create workers from a policy.
`runeward cohort add <prompt>`	Queue a task.
`runeward cohort run`	Idle workers run queued tasks in parallel.
`runeward cohort build <prompt>`	Add a task and run it.
`runeward cohort exec <prompt>`	Run in one pinned sandbox, so work accumulates.
`runeward cohort status`	Show workers and the board.
`runeward cohort export [dir]`	Copy workspaces to the host.
`runeward cohort down`	Tear down.

Set the agent with AGENT and MODEL (e.g. AGENT=codex MODEL=gpt-5-codex). With a shared token or RBAC, set RUNEWARD_TOKEN to the worker's token; the example drivers never store it in .runeward-fleet.

Example

Each worker has its own /workspace. Use exec to keep iterating on one app; use add and run to fan out independent tasks.

AGENT=claude MODEL=sonnet runeward cohort up
runeward cohort exec "Build a FastAPI todo API in app/ with SQLite and pytest"
runeward cohort exec "Now add a PUT /todos/{id} endpoint and tests"
runeward cohort export ./out

run, build and exec create agent sessions whose redacted transcript you can reopen in the dashboard. See Resumable agent turns.

Coordination

Agents never talk peer to peer. Workers claim tasks under a lease and heartbeat; a dead worker's lease expires and its task is reclaimed. This is the same on Docker and Kubernetes.

A group can mix providers (Cursor, Codex, Claude) and keys. For a local OpenAI-compatible model (Ollama, LM Studio), allow its endpoint in egress and set the agent's base-URL variable. See examples/build-fleet.toml.

Written from docs/fleets.md at commit 1ee29ff4ab36. Rune Box is open source under Apache-2.0.