herdr

Solid

Manage Herdr workspaces, tabs, and panes for Agent Toolkit swarms with eager windows, shell-aware execution, and reuse.

AI & Automation 14 stars 4 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

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

Skill Content

# Herdr Operate Herdr as the primary UI for `agent-toolkit swarm` — eager tabs, shell-consistent execution (`zsh`/`bash` via `_user_shell()`), and clean reuse of windows. This skill is the Herdr complement to `swarm` and `swarm-observer`. ## When to use - Swarm was started with `--ui herdr` (default) and you need to inspect or recover Herdr state. - `herdr workspace list/create/tab create/pane run` behavior is unexpected (extra workspaces `w7-wA` for `headless`, wrong `--cwd`, or missing eager windows). - User prefers Herdr over tmux for its excellent interactive UX and wants to reuse tabs for sequential requests. ## Prerequisites - `herdr` CLI installed and daemon running (`herdr --version`, `herdr workspace list --json` works; `--json` may be unsupported on older binaries — fallback to text). - Swarm run exists: `.agent-toolkit/swarm/runs/<run-id>/state.json` with `ui: herdr`. - Repo is a Git directory (worktrees are created under `.agent-toolkit/swarm/runs/<run-id>/worktrees/`). ## Workflow ### 1. Verify backend and shell ```bash agent-toolkit swarm doctor --json | jq '.backends' herdr --version echo $SHELL; getent passwd $USER | cut -d: -f7 # should be /usr/bin/zsh on this host # swarm's _user_shell() picks: $SHELL -> pwd.getpwuid -> /usr/bin/zsh -> /bin/bash ``` ### 2. Inspect Herdr state for a run ```bash herdr workspace list --json 2>&1 | jq '.[] | {id,name,path,status}' | head -n 40 # Expected: one workspace per run: swarm-20260807T...-<short> # Orphan chec...

Details

Author
ulises-jeremias
Repository
ulises-jeremias/agent-toolkit
Created
3 weeks ago
Last Updated
today
Language
V
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

herdr

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.

35 Updated today
mifunedev
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 yesterday
emateu
AI & Automation Listed

herdr

Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).

2 Updated today
atman-33