herdr

Solid

Drive the Herdr terminal workspace manager from the CLI inside the Open Harness sandbox — inspect and control workspaces, tabs, panes, agents, and git worktrees over the Herdr socket API, and read or steer other running agents headlessly. TRIGGER when: asked to run a `herdr` command, list/read/send to another agent or pane, check what agents are running or whether one is idle, split/focus/close panes or tabs, open or create a worktree in Herdr, wait for a pane's output or an agent's status, check Herdr server/session status, or install a Herdr provider integration. Do NOT trigger for tmux-managed headless services (cron, Slack gateway, watchdog) — those stay in their own tmux sessions.

AI & Automation 38 stars 3 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 83/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Herdr CLI Herdr (`herdr`, v0.7.4 in this image) is Open Harness's primary interactive workspace: a server process plus attached clients, with workspaces → tabs → panes, and agent-state detection per pane. This skill covers driving it from a non-interactive agent run. Operator-facing setup, persistence volumes, and the attach story live in `.oh/docs/integrations/herdr.md` — do not duplicate them here. Full subcommand catalog: `references/command-map.md`. Read it when you need a flag you do not already know; `herdr <group> --help` is the ground truth and prints a usage block for every group. ## Never do these from an agent run - **Do not run bare `herdr`, `herdr agent attach`, or `herdr session attach`.** They take over the terminal and hijack the operator's client. Use `herdr agent read` / `herdr pane read` to observe instead. - **Do not run `herdr update` or `herdr channel set`.** Herdr is pinned in the Open Harness image; upgrade by rebuilding against a reviewed release. - **Do not run `herdr server stop`.** It kills every attached client. Only the operator decides that. - **Do not read or write `~/.config/herdr/`** (config.toml, logs, `herdr.sock`). A `.config` path segment is denied to agent tooling repo-wide. Use `herdr config check` and `herdr status`, which report the same facts. - **Do not close, kill, or send text to a pane you did not create** without the operator asking. Other panes hold live agents mid-task. ## Output contract Socket-API-backe...

Details

Author: mifunedev
Repository: mifunedev/openharness
Created: 5 months ago
Last Updated: today
Language: TypeScript
License: Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

herdr

Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.

3 Updated 4 days ago

shttty

AI & Automation Featured

herdr

37,638 Updated today

ogulcancelik

AI & Automation Listed

herdr

Working knowledge of herdr (herdr.dev), the terminal workspace manager and coding-agent orchestrator (client-server, tmux-like persistence, agent state tracking). Use this skill whenever the user mentions herdr, asks about terminal workspaces/panes/tabs, attaching/detaching/resuming terminal sessions, orchestrating multiple coding agents, remote-attaching to another machine's terminal, or herdr config. ALSO use it proactively whenever HERDR_ENV=1 appears in the environment — that means you are running inside a herdr pane and can orchestrate panes/agents via the herdr CLI (e.g. spawn a real-TTY pane for interactive prompts like `op signin`).

0 Updated 2 weeks ago

emateu