codex-herdr
Router for controlling herdr from the Codex Desktop app only. The host application determines eligibility, not the model provider or model name. OMP running a Codex model is still OMP, not Codex Desktop. If the host is not known to be Codex Desktop, do not use this router; use the applicable native herdr skill instead.
"Herder" and "herder" in a request mean herdr; the CLI binary is always herdr.
Once the Desktop-only gate is satisfied, pick the workflow from the environment.
- Spawning an agent and handing it a task is dispatch. Read and follow the sibling
herdr-dispatchskill (../herdr-dispatch/SKILL.md) in either environment. The user's request that fired this skill is the explicit request it requires. - Inspecting or controlling existing panes, tabs, and agents needs the CLI reference. Check
echo "${HERDR_ENV:-unset}". IfHERDR_ENV=1, read and follow the siblingherdrskill (../herdr/SKILL.md). Otherwise use only the Follow-up commands inherdr-dispatch. - Verify connectivity first with
herdr workspace list; if it fails, herdr is not running. Report that and stop.
Boundary
The herdr skill's HERDR_ENV gate is intentional: it stops an outside shell from acting as if it owned the focused pane. Never set or fake HERDR_ENV to reach the native path, and never treat the focused pane as yours from outside. Outside Herdr, everything goes through herdr-dispatch.