For AI agents: the complete documentation index is available at /cafleet/llms.txt, the full documentation bundle is available at /cafleet/llms-full.txt, and this page is available as Markdown at /cafleet/concepts/overview.md.
CAFleet

    Overview

    CAFleet multiplexes independent coding-agent sessions in tmux or herdr. Use its CLI and skills to delegate research, implementation and review, then collect durable replies while your host continues the task.

    Core terms

    TermDefinitionReference
    fleetA namespace identified by a non-secret integer fleet_idFleet isolation
    root DirectorThe current session registered by fleet creation; owns assignments and team lifecycleMember lifecycle
    memberAn independent coding-agent session registered in a fleetMember lifecycle
    placementThe association between a member and its multiplexer session, window, pane and backendData model
    brokerThe synchronous SQLite data-access layer used by the CLIStorage
    messageOne point-to-point delivery, consumed through input_required → completedMessage envelope
    inline previewA literal one-line notification submitted Escape-first into an ordinary recipient's pane, carrying the full body or a show pointerNotifications
    receiveA finite inbox wait for scripts and manual use that also retries ordinary-member previewsMessage wait
    inbox streamA persistent read-only JSONL observer of pending messages with explicit ACK consumptionMessage listen
    coding-agent backendThe selected agent binary recorded in a placementCoding agents

    Fleet isolation

    Use the literal IDs returned by the CLI. A fleet partitions routing within the local trust model; it supplies no authentication. Members of a fleet share the selected database URL. Cross-fleet sends fail with members {from} and {to} are not in the same fleet.; missing destinations fail with Destination member not found: {to_id}.

    Fleet creation atomically registers the calling Director and its current pane. You can create an ordinary member immediately afterward. The Director owns pane teardown and deletes its members before deregistering the fleet.

    Responsibilities

    OwnerResponsibility
    HostContinue its task and own native shell/background results
    DirectorAssign work, receive replies, inspect evidence, resolve blockers and close the team
    CLIRegister sessions, persist messages, stream inbox records, preview ordinary-member messages and submit authorized pane input
    MultiplexerSplit, read, type into and close panes while preserving layout ownership
    MemberPerform its assignment, report through the broker and route required unavailable commands

    The CLI reference owns the command registry. The product ships as a CLI with embedded skills/presets and this documentation site.

    Receiving delegated work

    The Director owns one native inbox receiver, reconciles full broker records, ACKs consumption and keeps deferred actions in host-owned task state. Ordinary members receive pane previews. Native reception preserves supplied goal controls and user decision gates; the fleet guide explains handle ownership, recovery and manual reception.

    Design document workflow

    The bundled design-document workflows preserve clarification, independent review, TDD and explicit user approval. Follow the design document guide.