herdr-fleet
Optional host integration for Herdr: shared skills, lane configuration, account-manager forwarding, taskr roles, resource admission, and staged service assets. Load alongside herdr-orchestration.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- herdr-fleet
- description
- Optional host integration for Herdr: shared skills, lane configuration, account-manager forwarding, taskr roles, resource admission, and staged service assets. Load alongside herdr-orchestration.
03 SKILL.md 正文
Herdr fleet
Load local.md if it exists beside this file
(~/.agents/skills/herdr-fleet/local.md). It contains the operator's private
policy, accounts, host names, and restrictions. The installer detects this
overlay without reading or replacing it. Never copy it into a public artifact.
Private ~/.config/herdr-fleet/instructions.local.md is the one source of operator model policy and bans. With it present, --fleet regenerates the global instructions of existing Claude/Codex directories as public base plus overlay on every run; a hand-edited copy is saved once as <file>.herdr-setup-prev and replaced, and a 0444 file stays 0444.
Installation
The canonical installer is products/taskr/install.sh in herdr-kit.
Default installation includes the taskr CLI and TUI, the taskr skill, and a staged Herdr plugin.
--fleet adds orchestration/fleet skills, launch helpers, minimal taskr hooks,
and staged service assets. products/setup/install.sh delegates to that entry
point with --fleet. Core services and the taskr plugin require manual activation; the explicit radar
opt-in manages its external plugin.
Skills live at ~/.agents/skills/<name>. Existing Claude, Codex, and OpenCode
config directories receive loader links. Regenerate the upstream Herdr skill
with herdr --skill after a Herdr upgrade; the installer does this when available.
The shared placer keeps ~/.local/state/herdr-setup/installed and
~/.config/herdr-setup/keep. Identical files are skipped; recorded, unedited
files update; edited files receive .herdr-setup sidecars. Resolve those by hand.
Use --keep .codex/hooks.json, for example, to preserve a machine's settings.
Lanes
herdr-launch, herdr-lead and herdr-hub read the same generic lanes.json.
An optional ~/.config/herdr-fleet/lanes.json replaces the entire table.
The installer never reads or writes the private table. Configure model choices,
role prefixes, and restrictions there; it is the only list of models
(herdr-launch --lanes). Write per-model policy in the instructions overlay.
Unknown or malformed lanes fail before registration or agent startup.
For every Herdr read, send, close or launch on another host, use herdr --machine <label> (upstream Herdr skill: "To control a saved SSH machine"); start a remote lane with herdr-launch --machine devbox.
Use ssh only for non-Herdr work, such as git, files and slotr.
Optional tools
--codator selects the cdx/cdl forwarding wrappers; it never installs Codator.
--practices and --verification add the optional skill packs. --slotr,
--notifications (public Moshi hook fragments), and --radar (the external
pinned plugin) are separate opt-ins; missing optional tools do not block the core.
The hub (FLEET_ROLE=hub) keeps Moshi notifications; leads and helpers (FLEET_ROLE=worker) stay quiet.
Launch helpers forward Codex and Claude through an existing ~/.local/bin/codator; they
never install it or read its accounts. For a resume, preserve the recorded account and native session.
Do not bypass an account manager's refusal or inspect credential files.
If a host uses slotr, a leaf brief gets no slotr run line except the one
focused repro that a gate failure prompt names. A parent's local head gate passes
--cost MIB or an existing --kind.
Keep local admission configuration and notification credentials outside this repo.
The default hook templates call taskr; the Claude template also denies Agent,
Task and Workflow under HERDR_ENV=1 (Codex has no such hook). Public notification
fragments are selected explicitly.
Private notification additions belong in locally kept settings.
taskr roles
--taskr-hub (implies --fleet) stages the tailnet dashboard address and user service.
--taskr-client http://hub.example.ts.net:7788 (implies --fleet) stages a client URL.
Existing ledgers and incompatible roles require manual reconciliation.
The installer prints activation steps and never starts or restarts a service.
04 同仓库更多 Skills
taskr
Report progress/questions/completion and orchestrate Herdr campaigns through the task ledger.
taskr
Report progress/questions/completion and orchestrate Herdr campaigns through the task ledger.
herdr-orchestration
暂无简介
herdr-fleet
暂无简介
herdr-verification
Author or maintain a project verification map using its existing driver, real user paths, and durable evidence.
herdr-practices
An on-demand reference index for research, review, measurement, fix verification, and retrospectives; not always-on and not a mode.