> A native home for Claude Code, Codex and every coding agent. Every pixel is a file your agent can change. Close it, they keep working.
First two sentences give zero information what it does. Third one is useful but i think many harnesses do it?
Continuing:
> A new kind of agent workspace. Native and terminal first, with nothing between you and your agents. Every part of it is a plain folder your agent can rewrite, and every agent keeps running when the window is gone.
Okay, more of the same. Let's press on.
> Your agents run agents. And hear back.
> An agent hands work to helpers and keeps going. When they finish, their reports land in its input. No copy-paste between windows: herdr-core carries the messages.
Are there modern harnesses that don't do subagents/subthreads/whatever the same way?
---
There are some interesting bits but the vibed copy is for me offputting and a sign even the author might not understand what he made.
Yeah that copy is pretty bad. My understanding (someone correct me if I'm wrong), but the herdr native app is an improvement over the existing TUI multiplexer, with a new API for facilitating comms between agents. Herdr is really useful if you've not tried it. I'll be giving this a go (I hadn't really been using agent comms between panes anyway, more just for workspace navigation). Seems you can think of herdr as a 'harness for your harnesses'!
What's useful about Herdr compared to tmux and claude code or codex's built in sub-agents?
I suppose it is just the convenience of having an opinionated app that works with agents out of the box, tmux could be more powerful but similar to vim vs vscode, you need to tune it in.
My question also!
It does read a bit like Claude was wondering around homeless in a foreign land and now has a native home. Good for him I suppose, immigration is not a fun process these days.
It does sound like that now that I think about it.