herdr

Control herdr workspaces, tabs, and panes via a local unix socket.

1|Updated Jul 22, 2026
One-click install
npx skills add https://github.com/wyattjoh/skills --skill herdr-wyattjoh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: herdr
Source: https://github.com/wyattjoh/skills/tree/main/skills/herdr
Command: npx skills add https://github.com/wyattjoh/skills --skill herdr-wyattjoh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of managing complex, multi-agent terminal environments by providing a programmatic interface to control workspaces, tabs, and panes.

Core Features & Use Cases

  • Workspace Orchestration: Create, rename, and switch between project contexts dynamically.
  • Cross-Pane Control: Split panes, execute commands in background processes, and monitor output or agent status in real-time.
  • Use Case: Automate a development workflow where an agent spawns a server in one pane, waits for it to be ready, and then runs a test suite in a separate pane.

Quick Start

Use the herdr skill to split the current terminal pane to the right and execute a development server command in the new pane.

Frequently Asked Questions about herdr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate terminal workspace orchestration for multi-agent coordination?

Terminal workspace orchestration automates multi-agent coordination by using a local unix socket to programmatically control workspaces, tabs, and panes for background task execution. It enables dynamic management of project contexts and cross-pane command execution.

Can I split terminal panes and run background commands for automated workflows?

You can split terminal panes and run background commands by sending instructions through the multiplexer interface. This allows an agent to spawn a server in one pane, monitor its output, and execute test suites in a separate pane automatically.

What is a terminal multiplexer programmatic interface and when do I need it?

A terminal multiplexer programmatic interface provides automated control over terminal workspaces via a local unix socket. You need it when managing complex, multi-agent terminal environments that require dynamic workspace creation, tab switching, and real-time pane monitoring.

Do I need the herdr binary in my system PATH to control terminal workspaces?

You need the herdr binary present in your system PATH and an active herdr-managed environment to control terminal workspaces. Without this prerequisite, the programmatic interface cannot communicate with the local unix socket to manage panes and tabs.

What's the best way to manage multiple terminal agents across different project contexts?

The best way to manage multiple terminal agents across project contexts is using a programmatic multiplexer interface to dynamically create, rename, and switch workspaces. This enables automated cross-pane control and real-time monitoring of background tasks.

Why does my terminal automation fail without an active multiplexer-managed environment?

Terminal automation fails without an active multiplexer-managed environment because the programmatic interface requires a local unix socket connection. The herdr binary must be running in the system PATH to receive workspace, tab, and pane control commands.