AiSulivo
AiSulivo
Menu
AiSulivo
AiSulivo

herdr

Keep coding-agent terminals organised and persistent with herdr’s background runtime.

Pricing
Public hosted pricing not verified
Free plan
Installation available; current license and hosted terms require confirmation
Platforms
macOS, Linux, Windows, CLI

Tool Information

herdr
herdr
Updated: September 2026
Tool type: Coding Agent Runtime
Pricing: Public hosted pricing not verified
Free plan: Installation available; current license and hosted terms require confirmation
Platforms: macOS, Linux, Windows, CLI
Login required: Local runtime setup; agent-provider accounts may be required
API: Yes; CLI and socket API
Browser extension: No official browser extension verified
Mobile app: No official native mobile app verified
AI models: Underlying model versions not publicly specified
Developer: herdr

About herdr

herdr is a runtime for coding agents that already run in a terminal. It owns the terminal sessions and keeps them organised inside a background server, rather than replacing the agent with another coding model. The goal is to make several ongoing development tasks easier to follow without keeping every client window attached.

Persistent workspaces

The official site describes workspaces containing agent panes and ordinary development processes. Closing a client or losing its network connection does not itself end the server-side session. After a machine restart, herdr restores the layout and resumes supported sessions; that is different from a process continuing to execute while its host is powered off.

Status detection identifies agents as working, blocked or idle. A developer can use that overview to find the session needing an answer instead of inspecting every pane manually. Long-running jobs and development servers can remain visible alongside agent activity.

Agent-native control

The CLI and socket API expose the same control surface used by agents. They can manage panes and coordinate supported sessions through structured operations. The project advertises compatibility with existing clients such as Claude Code, Codex, Cursor and OpenCode on macOS, Linux and Windows.

Those integrations do not include the underlying model subscriptions automatically. Credentials, agent permissions and execution costs remain relevant to the tools running inside the terminals.

Trying the runtime

Start with a noncritical repository and one familiar agent. Verify reconnection, status reporting and restart behaviour before depending on unattended work. Keep normal code review and command-approval practices in place, because organising an agent’s terminal does not establish that its changes are correct or authorised.

Key features
  • Persistent agent terminals
  • Workspace organisation
  • Working and blocked status
  • CLI control
  • Socket API
  • Cross-platform runtime
Use cases
Persistent agent terminals,Workspace organisation,Working and blocked status,CLI control
How to use
  1. Read the official installation instructions.
  2. Choose the supported operating system.
  3. Install the runtime.
  4. Open a noncritical workspace.
  5. Launch a familiar agent CLI.
  6. Check status and reconnect behaviour.
  7. Inspect proposed code changes.
  8. Expand to additional sessions after testing.
Best for
Coding Agent Runtime Users
Integrations
Claude Code,Codex,Cursor,OpenCode and other agent CLIs
Commercial use
Development use subject to runtime license and separately licensed agent services

Related Tags