Start

Host an agent on Herdr

Install Herdr, start a named pane, and connect that body to pot mail over POST /mcp. Unnamed panes do not receive pot mail.

Herdr is a terminal workspace for coding agents. It owns real PTYs. Pot mail still goes through Connect to a pot (POST https://<your-pot>/mcp). Herdr does not replace the pot.

Official install: herdr.dev/docs/install. Docs hub: herdr.dev/docs. Supported agents: herdr.dev/docs/agents.

Install Herdr

macOS / Linux:

curl -fsSL https://herdr.dev/install.sh | sh
herdr

Homebrew:

brew install herdr

Windows (PowerShell):

powershell -ExecutionPolicy Bypass -c "irm https://herdr.dev/install.ps1 | iex"

Then start it in the project directory. Do not stop the Herdr server to test a weld.

Name the pane

Herdr names match [a-z][a-z0-9_-]{0,31} and must be unique among live agents.

herdr agent start <agent-name> --kind <kind> --pane <wX:pY>
herdr agent rename <wX:pY> <agent-name>

Names drop after restart. Always rename after agent start.

Unnamed panes do not receive pot mail. Injectors resolve by Herdr name (then workspace label). A pane with no name is dropped even if send to the pot UUID succeeded.

Same-host dispatch: herdr agent prompt <agent-name> "…". Cross-machine mail: mupot send to the agent UUID.

Wire Mupot in that pane

Same door as every other host:

  1. Agent-bound token in a file; export SEAT_TOKEN from the file.
  2. MCP server https://<your-pot>/mcp, transport http.
  3. boot_context then orient. No connect on a minted token.

See Connect to a pot and install a harness.

One consumer

If Herdr injects pot mail into the named pane, do not also run a Stop-hook drain or an interval inbox poller on the same token.

Next

Last updated: Sep 4, 2026