4. Setup

Status: ⚫ Superseded by 13 User Guide §2 (2026-08-17). This page was written in the design era as a scope note and the procedure was never filled in. Its content had gone wrong in every detail — a decommissioned model host, port 8080, herdr protocol 14, a systemd unit that does not exist on this host, Redis Streams / NATS that were never built. Rather than leave those claims in place, the page now points at the written procedure.

Go to 13 User Guide → §2 Install. It covers, against the running system:

herdr, and why you check the protocol number rather than the version;
building and starting the daemon;
the login shell rule for ${SHARED_ENV}/tools/secrets.sh — the single most expensive trap in bring-up, and why scripts/fleetd-launchd-wrapper.sh exists;
the lead's tab label, which is how the daemon resolves who the lead is.

The one rule that was already right on this page

The lead host and process must never be given ANTHROPIC_BASE_URL or ANTHROPIC_AUTH_TOKEN. Only member panes carry them, and only the daemon sets them, at spawn. See Architecture → Subscription boundary.

13 User Guide · 2 Message Server · 1 Architecture · 11 Features

📖 fleet

Home — overview & the decision

Chapters

Architecture — system · 2 invariants · 2 modes
Message Server — the fleetd design
Approaches — transports compared, why herdr
Setup — ⚫ superseded by 13
Operations — ⚫ superseded by 13
Team — orchestrating a mixed fleet
Use Cases — the review scenario + mechanisms
Roadmap — delivery record: what is live, what is off, what was dropped
Implementation — as-built code map · classes · flows · state machines
Cross-Host Messaging — broker topology · exchanges · queues per entity
Features — what it can do · the knob that turns it on · why · the gotcha
Claude → OpenCode — porting a workspace to a second host
User Guide — 🟢 install · configure · run · delegate · the traps
Fleet Manager — many fleets on one host, over REST
REST API Reference — all 14 routes, roles, and bodies
Security & Trust Boundary — the guard · authz · what a member inherits

Design proposals (not built)

CB-548 Lead Quorum — a deterministic decision procedure around a lead's judgment

🟢 herdr-centric fleetd · AgentAPI = research, never built

4. Setup

The one rule that was already right on this page

Related

📖 fleet