ClawIDE vs Herdr
An Apache-2.0 Rust terminal UI where a server owns your agent terminals, versus the same always-on idea in a browser, with an editor, reviews and tasks.
TL;DR
Herdr and ClawIDE share an idea: a server owns your agent terminals, and you attach from wherever you are.
Herdr is an Apache-2.0 Rust terminal UI with agent state detection, a socket API and a large plugin marketplace. ClawIDE puts that model in a browser: it adds a file editor, merge review, a task board and model gateways for free, and tracker sync and Symphony-compatible runs on Pro for $5/mo.
At a glance
- What it is
- Self-hosted web app served by a single Go binary
- License
- Closed source, free binary (EULA)
- Price
- Free for the whole local workspace; Pro $5/mo, $48/yr or $99 once
- What it is
- Rust terminal UI for macOS and Linux (Windows in beta); a server owns the terminals and clients attach and detach
- License
- Apache-2.0
- Price
- Free; Herdr Cloud has a waitlist and no published price
ClawIDE
Herdr
| Capability | ClawIDE | Herdr |
|---|---|---|
| License | Closedfree binary | Apache-2.0 |
| Paid plan starts at | $5/mo | NoneCloud waitlist |
| Unlimited projects on the free plan | Yes | Yes |
| Git worktree per task, free | Yes | Yes |
| Browser UI from any device, nothing to install on the client | Yes | No |
| Single binary or headless server | Yes | Yes |
| Sessions persist when you disconnect | Yestmux | Yes |
| Agent CLIs supported | Unlimited17 presets | 21 |
| Model gateways (OpenRouter and others) | Yes13 + custom | No |
| File editor | Yes | No |
| Diff and merge review | Yes | No |
| AI code review | Pro | No |
| Markdown task board in your repo | Yes | No |
| Linear, Jira or GitHub Issues | Pro | No |
| Symphony WORKFLOW.md orchestration | Pro | No |
| Scheduled loops and automations | Pro | No |
| Usage and cost analytics | Yes | No |
| Checkpoints and rollback | Yes | No |
| Push notifications to your phone | Pro | Partialplugin |
| MCP server manager and debugger | Yesdebugger is Pro | No |
| Embedded browser with an element picker | No | No |
| Detects when an agent is working, blocked or done | Partial | Yes |
| Plugin, socket or CLI API | No | Yes |
Checked September 2026 against herdr.dev, github.com/herdrdev/herdr. Out of date? Email support@clawide.app.
Who each is best for
Choose ClawIDE if
- You’d rather open a browser tab than a terminal client, including from a phone or tablet.
- You want an editor, diffs and merge review next to your agents.
- You plan work on a task board, or in Linear, Jira or GitHub Issues.
- You route agents through a model gateway such as OpenRouter or Ollama.
Choose Herdr if
- You live in the terminal and want a small, fast TUI.
- You need an open-source (Apache-2.0) tool.
- You want each agent’s working, blocked or done state rolled up per workspace.
- You want to script it through a socket API, extend it with plugins, or drive several machines over SSH.
Moving from Herdr
Herdr and ClawIDE can run side by side on the same machine. Herdr’s sessions don’t move into ClawIDE, so start new work in ClawIDE and let running sessions finish.
- Install ClawIDE and make sure
tmuxis installed. ClawIDE keeps every pane in tmux. - Import the repos you use as Herdr workspaces as ClawIDE projects, then create a feature workspace (a git worktree) per task.
- Pick the same agent CLIs you ran in Herdr. They keep their existing config.
- If you reach Herdr over SSH, reach ClawIDE the same way with a port forward:
ssh -L 9800:localhost:9800 <host>, then openhttp://localhost:9800.
Your agents, on your hardware, in any browser.
Install the binary, run clawide, and open localhost:9800. The setup wizard finds your agent CLIs and projects. Every install includes a 14-day Pro trial.
curl -fsSL https://www.clawide.app/install.sh | bash