#Coding agents

cafleet supports three coding-agent binaries inside member panes. The backend is selected per member with --coding-agent {claude,codex,opencode}, and mixed-backend teams are allowed: a single Director may spawn all three in the same fleet with no broker-level differences. The value is recorded in the placement's coding_agent column.

The flag means slightly different things per command:

• cafleet fleet create --coding-agent is required, operator-declared metadata — cafleet does not spawn the root Director's process and cannot auto-detect what is already running in the calling pane, so the operator states the backend the Director is actually running on.
• cafleet member create --coding-agent both selects which backend is spawned and is recorded as placement metadata. When the flag is omitted, the member — every role — inherits the spawning Director's placement backend (an explicit value still wins).

Each backend is spawned with flags that enable its Bash tool with no runtime permission prompts. The per-backend spawn argv, shell-command posture, and sandbox trade-offs are specified in Coding-agent backends § Spawn argv.

#cafleet usage from a member pane

The cafleet CLI works unchanged from any backend pane. Identity reaches a member through its spawn prompt: cafleet member create renders four identity placeholders to literals, so the member reads its ids as plain text lines (e.g. FLEET ID: 1, YOUR MEMBER ID: 4) and passes them explicitly on every command. Each placeholder and its label line is in CLI options § Spawn-prompt substitution. The only environment variable forwarded into the pane is CAFLEET_DATABASE_URL. All three honor a leading-! shell shortcut on the coding agent's input line, so cafleet member prompt --shell works against any pane shape. For the full broker CLI reference, see CLI options.

#Model selection

cafleet member create --model <string> forwards the value to the spawned backend's own --model flag — e.g. --model opus for a claude member; omit it and the binary uses its own default. Per-backend accepted formats and create-time validation are in Coding-agent backends § Model selection.

#Reasoning effort

cafleet member create --effort <level> forwards a reasoning-effort level to the spawned backend binary. Unlike --model, the accepted level set is validated per backend at create time, before any registration or multiplexer side effect; omit the flag and the binary uses its own default. Per-backend accepted levels, forwarding forms, and rejection strings are in Coding-agent backends § Reasoning effort.

#Known asymmetries (intentional non-goals)

These are intentional non-goals, not gaps.

--effort with the opencode backend exits 2 with opencode does not support reasoning effort. before any side effect. Because codex and opencode panes do not display the member name, the pane_id column of cafleet member list is ground truth for all three. Operators who need kernel-enforced isolation should use the codex backend.