CAFleet

    Run a mixed-backend team

    A single Director can spawn claude, codex, and opencode members in the same fleet — there are no broker-level differences between the backends (Coding agents). This guide creates a fleet with one member per backend and messages each of them.

    Prerequisites

    • The backend binaries you want to mix (claude, codex, opencode) are on PATH — member create exits 1 with Error: binary <name> not found on PATH otherwise.
    • You have followed Quickstart § Install and Quickstart § Configure, and you are inside a tmux or herdr session (the multiplexer backend is auto-detected — see Multiplexer backends).

    Prompt

    Create a CAFleet team for this repo with three members — one on claude,
one on codex, and one on opencode. Name them alice, bob, and carol.
Once they are up, send each member a message asking it to report its
backend, and confirm all three reply. Then tear the team down.

    Your agent loads the cafleet skill and follows its Director-only supervision protocol before spawning members.

    The supervision tick is supplied by the monitoring member's cafleet monitor loop and works the same on any backend (claude, codex, or opencode); the monitoring member is the first cafleet member create (--role monitor), and the Director never runs the monitor itself (Monitoring).

    What to expect

    The agent creates a fleet, then opens three multiplexer panes — one per backend — each running its member's coding agent. Each message lands as a 2-line inline preview keystroked into the recipient's pane (Push notifications), so you watch every member wake up and reply. Only the claude pane shows the member name in its pane title (Coding agents). When all three replies are confirmed, the agent closes the panes and deletes the fleet.

    Appendix: the CLI underneath

    The commands the agent runs, with literal ids — fleet 1, root Director 2, members 3/4/5; your ids will differ.

    Expand the walkthrough

    Create the fleet — the operator declares the binary running in your pane via --coding-agent because cafleet cannot auto-detect it (Coding agents):

    cafleet fleet create --name "demo" --coding-agent claude
    1 director=2

    Spawn one member per backend:

    cafleet member create --fleet-id 1 \
  --name "alice" --description "claude member" \
  --coding-agent claude --text "You are alice. Wait for instructions."
    3 alice backend=claude pane=%7
    cafleet member create --fleet-id 1 \
  --name "bob" --description "codex member" \
  --coding-agent codex --text "You are bob. Wait for instructions."
    4 bob backend=codex pane=%8
    cafleet member create --fleet-id 1 \
  --name "carol" --description "opencode member" \
  --coding-agent opencode --text "You are carol. Wait for instructions."
    5 carol backend=opencode pane=%9

    List the panes — only the claude pane titles itself with the member name (Known asymmetries), so use the pane_id column to locate bob and carol:

    cafleet member list --fleet-id 1
    4 members:
  member_id  name           kind      backend   pane_id  idle
  ---------  -------------  --------  --------  -------  ----
  2          Director       director  claude    %0       -
  3          alice          member    claude    %7       -
  4          bob            member    codex     %8       -
  5          carol          member    opencode  %9       -

    Message each member — repeat with --to-member-id 4 and --to-member-id 5; the envelope and the 2-line inline preview are identical for every backend (Push notifications):

    cafleet message send --fleet-id 1 --from-member-id 2 --to-member-id 3 --text "alice: report status"
    Message sent.
[10 | from:2 | 2026-06-11T09:05:00.123456+00:00]
alice: report status

    Tear down — repeat member delete for members 4 and 5, then delete the fleet:

    cafleet member delete --fleet-id 1 --member-id 3
    Member deleted.
  member_id:  3
  pane_id:    %7 (killed)
    cafleet fleet delete --fleet-id 1
    Deleted fleet 1. Deregistered 1 members.

    Every member create / member delete flag and exit code is documented in CLI options.