herdr-orchestration

Featured

Orchestrate Claude and Codex worker TUIs from a controller agent — one worker per named herdr tab, driven over the herdr socket CLI.

AI & Automation 2,894 stars 189 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# herdr Orchestration The top-level agent is the **controller** (Codex, Claude, Fable, or another); it delegates to **worker** TUIs that gather evidence, draft bounded patches, run tests, and report. The controller owns assignment, state, conflict control, verification, integration, and the final user-facing answer. herdr is the substrate: each worker TUI owns a named tab, and the socket CLI (`herdr …`) gives the controller placement, input, screen reads, and native agent-status waits. ## One worker, one named tab Every worker gets its own tab, labeled at creation with `tab create --label`. The tab bar is the controller's dashboard: a labeled tab says which model is running which slice, and stays readable no matter how many workers are live. Tabs also cost no screen area. A split pane divides the caller's screen with every worker, and on a laptop the third worker leaves every pane too narrow to read. Split a pane only when the user explicitly asks to watch a worker beside the caller. Two names per worker, both required at launch: - **tab label** — `<model>: <slice>`, e.g. `opus: fix loops`, `codex: audit auth`. Free text; keep it short, tab bars truncate. - **agent name** — the slice as a slug, e.g. `fix-loops`. Must match `[a-z][a-z0-9_-]{0,31}` and be unique among live agents. Every `agent …` verb accepts it in place of a pane id. ## Workers are TUIs — no headless runners A worker is an interactive TUI — `claude` or `codex` — started with `herdr agent start`, ...

Details

Author
compozy
Repository
compozy/compozy
Created
7 months ago
Last Updated
today
Language
Go
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

herdr-orchestrator

Orchestrate coding agents through Herdr as the user's authorized proxy from Codex CLI, Claude Code CLI, or Grok Build CLI. Use only when the current CLI is already running inside Herdr and the user explicitly asks to use Herdr to delegate, parallelize, coordinate, monitor, redirect, test, review, or collect work from other coding agents. Do not trigger for an ordinary implementation, test, or review request that does not name Herdr or Herdr-managed agents. Worker prompts and replies must read as direct user-agent conversation. Requires HERDR_ENV=1, HERDR_PANE_ID, and explicit user authority to control agents.

6 Updated 3 months ago
hapo-nghialuu
Code & Development Listed

herdr-orchestrator

Orchestrate coding agents through Herdr as the user's authorized proxy from Codex CLI, Claude Code CLI, or Grok Build CLI. Use only when the current CLI is already running inside Herdr and the user explicitly asks to use Herdr to delegate, parallelize, coordinate, monitor, redirect, test, review, or collect work from other coding agents. Do not trigger for an ordinary implementation, test, or review request that does not name Herdr or Herdr-managed agents. Worker prompts and replies must read as direct user-agent conversation. Requires HERDR_ENV=1, HERDR_PANE_ID, and explicit user authority to control agents.

6 Updated 3 months ago
hapo-nghialuu
Code & Development Listed

herdr-orchestrator

Interactive Herdr setup and orchestration for a Grok pane coordinating Codex and three non-OpenCode Council agents.

3 Updated 1 weeks ago
vraj-ai