Herdr Orchestration

Treat the current agent session as the control tower, regardless of its CLI or model. Keep decomposition, routing, integration, user communication, and final review in this host session.

Load and follow the herdr skill before issuing Herdr commands. Continue only when HERDR_ENV=1, and use the installed CLIs as the authority for supported launch options. Herdr's discovery commands print their help and exit 2; treat that as success for discovery and do not run them under set -e.

Topology

The herdr skill governs command mechanics and safety. Where its defaults disagree with this skill — sibling-pane topology, no new tabs, moving the control tower to another workspace, or its --wait-at-prompt guidance — this skill wins: an orchestration run is an explicit request for this topology and this dispatch behavior.

Home workspace

Every run has one home workspace, which holds its control tower and every worker it starts, so the sidebar shows each piece of work in one place:

• Worktree work (one ticket or branch in its own Git worktree): home is that worktree's workspace, and it holds nothing but this run.
• Cross-worktree work (a release, a merge train, a UAT walk): home is repo main, the workspace on the repo's main checkout, which the sidebar shows as the parent of the repo's worktree group. Find it from any checkout of the repo; when this prints nothing, ask the user which workspace to use: