herdr Integration

herdr runs several coding agents side by side on one machine and tracks what each of them is doing. It organizes work into spaces — one per project, with tabs and panes inside. herdr is not another agent in ServerCC’s list; it is a runtime the agents live in, and ServerCC 2.0 connects to it.

Setup

The server page shows whether herdr is installed, next to the other tools. If it is missing, ServerCC can install it (the official script, into ~/.local/bin, no sudo); if a newer version exists, the app runs herdr update for you. The integration is built against herdr 0.8.

Spaces on the server page

While herdr is running on the server, its spaces appear on the server page in their own section. A space with an agent in it carries herdr’s own state word: working, blocked, done, or idle. These rows are discovered live — they are not workspaces yet and don’t count toward any limit.

Tapping a space opens a preview of the familiar workspace page. From there you can look around, attach to what is running, or adopt the space.

Attaching to a running agent

Tap a running agent session to attach to it: you see the same terminal herdr is showing, live, and can type into it. Attaching is free and doesn’t use any trial quota. When you leave, the app asks whether to Keep the session running in herdr or Stop it, which closes its pane.

Adopting a space

Swipe on a space row (or use the button on its preview page) to adopt it as a regular ServerCC workspace. Adoption goes through the normal workspace limit, and afterwards everything a workspace has works on it: session history, new sessions, the file browser, git diff, worktrees. The herdr sessions in that directory keep showing up on the workspace page, in their own section.

Launching agents inside herdr

When a workspace’s directory is one herdr manages, starting a new session offers herdr Mode: the agent launches in a fresh herdr tab instead of a plain tmux session, so it shows up in herdr with a state like everything else there. ServerCC always creates a new tab for it — it never drops an agent into a terminal you are using.

Worktrees work too: launching in herdr from a worktree goes through herdr’s native worktree open, so the checkout appears under its repo’s space rather than as a stray directory. Worktree rows in ServerCC likewise list the herdr sessions running inside them.

Per-agent status hooks

herdr learns an agent’s state (working, blocked, …) through a small hook installed into each agent’s own configuration. ServerCC’s herdr screen lists these integrations per agent with three states: not installed, current, or outdated — outdated ones get an Update button. A hook lives in that agent’s own config files on the server, so removing one asks for confirmation first.

See also: Supported AI Agents for the agents themselves, and Persistent Sessions for the tmux-based flow herdr Mode replaces.