herdr

Herdr

Herdr organizes terminals into workspaces, tabs, and panes, recognizes coding agents running inside panes, and exposes the current session through the herdr CLI.

Use local configuration and source references

On this machine, answer configuration and behavior questions from local evidence instead of relying on memory. Read local-machine.md for the evidence order and paths.

Start configuration questions with the commented managed file $DOTFILES/herdr-cfg/config.toml. It backs ~/.config/herdr/config.toml and documents the user's intentional overrides. Use herdr --default-config for the installed version's complete default configuration. For deeper behavior or documentation questions, inspect the local source checkout at $DOTFILES/herdr.

The source checkout may be ahead of the installed binary. Verify the relevant version before claiming that source or draft documentation describes installed behavior.

Read-only inspection of local config, documentation, source, and CLI help does not require a Herdr-managed pane. The following environment check applies before commands that inspect or control a live Herdr session.

Before issuing any control command, verify that this agent is running inside a Herdr-managed pane:

test "${HERDR_ENV:-}" = 1

If the check fails, say that you are not running inside Herdr and stop. Do not inspect or control the focused Herdr session from outside Herdr.

When the check passes, the herdr binary in PATH talks to the current session. Use it to inspect neighboring work, create terminal layout, start agents and commands, read output, and wait for state changes.

Learn the current CLI

The installed binary is the authority for command syntax. Start with:

herdr --help

Then print the relevant command group by running the group without a subcommand:

herdr agent
herdr pane
herdr workspace
herdr tab
herdr worktree
herdr terminal
herdr notification
herdr integration
herdr session
herdr machine