spawnlisted

# Spawn You are the **lead**. A spawned peer is a **full agent session** — its own context window, its own approval flow, its own lifetime, steerable by the user in a visible pane. That makes it a third kind of delegate, above the two the Codex library already has: | Tier | What it is | Lifetime | Reach it via | |---|---|---|---| | subagent | `spawn_agent` child — context isolation, same model | dies with the thread | `$46-orchestrate` | | one-shot | fresh `codex exec` / `claude -p` process | one turn, deliberately not resumable | advisor and peer scripts | | **spawned peer** | full interactive session, own pane + worktree | survives you; user-steerable | this skill | ## Preflight — the sandbox gate Everything here drives the herdr socket through the `herdr` CLI, and the socket lives outside the workspace (`~/.config/herdr/herdr.sock`). Gate first, fail closed: 1. `HERDR_ENV=1`? If not, you are not inside herdr — jump to Fallbacks. 2. `herdr status` — if it answers, you have socket access; proceed. 3. `Operation not permitted` or `PermissionDenied` under `workspace-write` means the Codex sandbox blocks the out-of-workspace socket (both directions verified 2026-08-06). Two honest paths, both routed through the user: switch to Full Access (`/permissions` in a live interactive session, or a relaunch with `--sandbox danger-full-access`, either only with their explicit authorization — a custom permissions profile can also allowlist this one socket), or print the exact command