herdr-pairlisted

Persistent Claude and Codex coworking inside one Herdr tab. Use when the user asks for Herdr pairing, another workflow needs a live peer, or input begins with `[agent` or includes `[herdr-pair control`. For inbound traffic, including after context compaction, run receive and reply through the bundled sender instead of local output.
hcaiano/skills · ★ 3 · AI & Automation · score 76

Install: claude install-skill hcaiano/skills

# Herdr Pair Pair Claude and Codex in one Herdr tab. Keep the pair and its `sid` alive across tasks, accepted work cycles, and context compaction. The user can read and interject in either pane. Write partner messages and user handoffs in the user's current language. Keep code, commands, paths, identifiers, errors, and protocol headers literal. ## Preconditions Set `SKILL_DIR` to this skill directory and `PAIR_SCRIPT="$SKILL_DIR/scripts/herdr-pair.mjs"`. Always use that absolute path; the project cwd is unrelated to the installed skill path. Require `herdr` with the agent automation commands (`herdr agent start`, `herdr agent prompt`) and `trash` on `PATH`, `HERDR_ENV=1`, and `HERDR_PANE_ID`. If any is missing, stop and tell the user to install or start (or update) Herdr. ## Guardrails 1. Scope every pane operation to the caller's exact `workspace_id` and `tab_id`. Never address a pane discovered only by workspace, focus, label, cwd, direction, or pane number. 2. Use `herdr-pair.mjs send` as the sole partner transport. Reserve normal assistant output for a header-free user handoff. `SendMessage`, subagent messaging, and direct pane writes are different channels. 3. Give one agent the write lease for each file scope: owner, target files, forbidden changes, validation, and stop point. The partner stays read-only on that scope until handoff. 4. A submitted user message overrides partner traffic. Surface any conflict in the next reply. One failed partn