← ClaudeAtlas

herdrlisted

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).
ogulcancelik/herdr · ★ 5,022 · Code & Development · score 81
Install: claude install-skill ogulcancelik/herdr
# herdr — agent skill before using this skill, check that `HERDR_ENV=1`. if it is not set to `1`, say you are not running inside a herdr-managed pane and stop. do not inspect or control the focused herdr pane from outside herdr. you are running inside herdr, a terminal-native agent multiplexer. herdr gives you workspaces, tabs, and panes — each pane is a real terminal with its own shell, agent, server, or log stream — and you can control all of it from the cli. this means you can: - see what other panes and agents are doing - create tabs for separate subcontexts inside one workspace - split panes and run commands in them - start servers, watch logs, and run tests in sibling panes - wait for specific output before continuing - wait for another agent to finish - spawn more agent instances the `herdr` binary is available in your PATH. its workspace, tab, pane, and wait commands talk to the running herdr instance over a local unix socket. if you need the raw protocol or full api reference, read the [socket api docs](https://herdr.dev/docs/socket-api/). ## concepts **workspaces** are project contexts. each workspace has one or more tabs. unless manually renamed, a workspace's label follows the first tab's root pane ��� usually the repo name, otherwise the root pane's current folder name. **tabs** are subcontexts inside a workspace. each tab has one or more panes. **panes** are terminal splits inside a tab. each pane runs its own process — a shell, an agent, a server, any