| name | herdr-setup |
| description | Use when installing, updating, configuring, or troubleshooting Herdr, including missing commands, PATH errors, version differences, or Pi integration setup. |
Herdr Setup
Use the installed binary as the source of truth. Do not assume a command or flag from a different version exists.
Inspect first
command -v herdr
herdr --version
herdr --help
herdr integration status
If herdr is absent, explain that it supports Linux and macOS. On Windows, the native preview installer is available; use WSL only if the native preview is unsuitable. Ask before running either upstream installer:
irm https://herdr.dev/install.ps1 | iex
curl -fsSL https://herdr.dev/install.sh | sh
After installation, start a new shell if PATH has not refreshed, then rerun herdr --version.
Integrate Pi
Inspect integration state before changing it:
herdr integration status
Install or update the Pi integration only when requested:
herdr integration install pi
Use herdr integration status --outdated-only to identify stale integrations. Do not remove an integration without confirmation.
Updates and configuration
- Use
herdr update only when the user asks to update.
- Use
herdr --default-config to inspect defaults before editing configuration.
- Treat
HERDR_CONFIG_PATH, HERDR_SESSION, and HERDR_SOCKET_PATH as explicit overrides; report their values before troubleshooting a surprising target/session.
Command or version mismatch
- Stop guessing after an unknown-command or unknown-flag error.
- Run
herdr --help, then <known-group> --help for the installed command tree.
- Read the upstream docs fallback, selecting the installed release version when available.
- If the installed help and matching version docs disagree, prefer installed help and report the discrepancy.
Safety
herdr server stop, session stop, session delete, and workspace/tab/pane close affect live work. List or inspect state first and ask for confirmation before running them.
