← ClaudeAtlas

herdrlisted

Run and manage AI subagents in herdr panes, and drive the herdr terminal workspace manager from the CLI. Use to start a subagent (claude, codex, omp, gemini, opencode, droid, copilot, cursor - or a preset of your own), send it a task, read its answer, hold a multi-turn conversation with it, list which agents are running and what state they are in, and stop one - one command per step, with the send/Enter and status-timing traps handled. Subagent definitions (argv, cwd, env, session, timeouts) live in agent config, so "run the reviewer agent" resolves to a preset rather than a guessed command line. Also covers the layout itself: list, focus, rename, create, or close workspaces, worktrees, tabs, and panes, and answer "which one am I in". Use whenever the user mentions herdr, asks to run / spawn / ask / message / check on / stop an agent or subagent, or asks to rename / switch / focus / close / list a session, workspace, tab, pane, or worktree - e.g. "run a subagent to review this", "ask the other claude what it
Max-Levitskiy/skills · ★ 0 · AI & Automation · score 66
Install: claude install-skill Max-Levitskiy/skills
# Driving herdr `herdr` is a terminal workspace manager for AI coding agents. It runs a background server and exposes everything over a CLI that talks to that server's socket. This skill covers reading and changing the layout, and driving other agents. ## The object model (read this first) ``` session (a named background server, own socket, own workspace tree) └── workspace ← the per-project / per-worktree unit. HAS THE LABEL in the sidebar. └── tab ← a tab within a workspace └── pane ← a terminal within a tab; where a shell or agent runs └── agent ← an AI agent (e.g. claude) attached to a pane ``` **The trap:** "rename **this session**", "what session am I in", "close that session" usually mean the **workspace** - the labeled sidebar item. Map "session" → workspace by default. But sessions are real and plural. A session is a separate server with its own socket and its own workspaces; users routinely run one per project, and `default` is often **stopped** while the work lives in named sessions. Every command here talks to *one* session - the one your pane is in. Workspace `w1` in `neochain` and `w1` in `personal` are different workspaces. Run `herdr session list` before assuming. | Object | id example | rename command | |-----------|----------------|---------------------------------------| | workspace | `w1` | `herdr workspace rename <id> <label>` | | tab | `w1:t1X` | `herdr