install

# Herder Install Install or verify the five host-native agent profiles required by Herder. The profiles are bundled with the installed plugin, so the plugin version is the single verified release unit and no runtime network fetch is required. Codex Fire uses these profiles as native custom agent types. It requires Codex Multi-Agent V2 and never falls back to nested `codex exec` processes. Claude Fire uses the bundled host-native agents directly. The bundled Codex Accountant uses Luna/max with Fast tier, and the Implementer also uses Luna with Fast tier. The Claude Accountant uses Opus/medium. Sol-backed roles and the parent coordinator remain on Standard tier. ## Invocation Interpret tokens after the skill name as installer arguments: ```text herder:install [--host codex|claude|all] [--scope project|user] [--dry-run] [--force] ``` - Default host: the current agent host. Pass it explicitly to the script; never infer a different host merely because its configuration directory exists. - Default scope: `project`. - `--force`: replace differing installed profiles after preserving backups. Never add it unless the user explicitly asks to replace or refresh customized profiles. Codex users invoke `$herder:install`; Claude Code users invoke `/herder:install`. ## Install 1. Resolve the skill directory to the directory containing this `SKILL.md`. 2. Identify the current host as `codex` or `claude`. If the user requests both, use `all`. 3. Run: ```bash node <skill-dir>/scripts/install-herder.mjs \ --host <codex|claude|all> \ --scope <project|user> \ <remaining user arguments> ``` 4. Report every installed, bundled, unchanged, or conflicted profile. 5. On Codex, report the installer's Multi-Agent V2 check. If it is disabled, explain that installation is incomplete for Fire and run `codex features enable multi_agent_v2` only with the user's authorization to change Codex configuration. Then, with the same authorization, replace the boolean feature entry with the namespaced configuration below. If the current release does not expose the flag, report that it is unsupported rather than suggesting an execution fallback. The host child capacity must reserve one Accountant slot in addition to Fire's requested plan-worker limit; default five-worker execution requires at least six child threads. 6. On Codex, require a new session when the agent directory was first created or profiles changed. Native custom agents and feature flags are resolved when a session starts. 7. On Claude, report that persistent accounting requires `SendMessage`. If it is absent in the current session, direct the user to start a new session with `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` before Fire; do not silently use repeated one-shot accountants. Codex project scope installs to `<repo>/.codex/agents/`; user scope installs to `~/.codex/agents/`. Claude agents load directly from the plugin's `agents/` directory, so the installer only verifies their bundled definitions. After installing defaults, direct users who want different native Codex models or Orca role routing to `$herder:configure`. Configured native profiles intentionally differ from the bundled defaults, so a later install reports conflicts and preserves them. Use installer `--force` only when the user explicitly wants to reset configured profiles to bundled defaults. ## Codex Requirement `$herder:fire` requires a live Multi-Agent V2 spawn interface that accepts a custom `agent_type`, persistent follow-up, and long waits. Codex's reserved generic spawn schema can hide custom-agent metadata, so Herder uses a dedicated namespace. Configure exactly one form of `multi_agent_v2`; replace `multi_agent_v2 = true` under `[features]` with: ```toml [features.multi_agent_v2] enabled = true hide_spawn_agent_metadata = false tool_namespace = "herder_agents" ``` Do not set legacy `agents.max_threads` with Multi-Agent V2. Use Fire's `--max-parallel` for plan-worker scheduling. If a host-level limit is needed, use `max_concurrent_threads_per_session` inside the block above and allow one additional Accountant thread; for example, `--max-parallel 5` needs a host limit of at least `6`. The installer checks the effective feature state through the current Codex executable, but it cannot inspect a session's already-frozen tool schema. Installing profiles does not silently edit `config.toml`; it prints the required configuration and a feature-enable command when configuration is missing. ## Conflict Policy Install automatically when a target is absent or byte-identical. If a target differs, stop without changing any profile and show the conflict. Preserve user customization by default. Use `--force` only with explicit user authorization; the installer saves replaced files under `<Codex config root>/.plan-herder-backups/<timestamp>/`, alongside rather than inside `agents/`, before writing the new set. On any install or verification run, migrate the unsafe legacy `agents/.herder-backups/` directory to a timestamped directory under that safe root; `--dry-run` reports the migration without changing files. Do not execute profile contents. Read only files named in the bundled manifest, require paths to remain inside the expected plugin profile trees, and verify every SHA-256 digest before writing anything.