FR version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
75% Positive
Analyzed from 846 words in the discussion.
Trending Topics
#herdr#account#why#don#running#multiple#machines#tailscale#agent#dev
Discussion (17 Comments)Read Original on HackerNews
I had always been curious on why Tailscale hasn't creating agent-oriented features. It's obvious to me that Tailscale is at the best position (AFAIK) to capitalize on agents demand.
Their connectivity product is unique. And it's a natural fit to connecting long-running agents instance across the Internet.
The limitation of Orca or Herdr is that they don't have integration for multi project work. Here is what I wanted
Telegram/OpenClaw → Single Linear Account Control plane with multiple projects → route each task to be completed and PRs open for review across multiple repos.
This is where Cyrus helps. You setup labels and routing so cyrus knows which gitrepo to build worktrees from, and the labels can help you pick up the right model (codex-sol/astro or claude-opus/fable). This has helped me be more hands off.
So I use both Orca and Cyrus. Cyrus for automation (telegram ingress) vs Orca if I want anything hands on.
I get that Herdr wants investors to give them money to own developers' coding sessions, but the value proposition ("Walk away and they keep working. Come back from any machine and they're where you left them.") seems like a miss since it's so easy to do that without them.
I'm surely missing something.
I haven’t tried herdr yet, but maybe it’s just not targeted at me?
The real problem I have with the remote codex setup is when it needs to authenticate as me. I sort of solved this for sudo and ssh with this [1], but I think something like this could be integrated deeper into the harness
[1]: https://github.com/evanpurkhiser/agent-witness
Oh, right, this is how we monetize in 2026. Nevermind.
is it, though?
I can imagine having a local Herdr instance and one running on a remote box somewhere, but I can't think of a use case where I'm trying to juggle N different Herdr instances and that overhead becomes a meaningful bottleneck.
> Getting to 1.0
> After this update, what I want is to make connecting those machines more convenient. You shouldn’t need to think about SSH or deal with complicated network setup. It should be easy to connect any machine, anywhere, through one Herdr account.
(emphasis added)
sigh. I'm a daily user of Herdr. I don't have a Herdr account today. I don't want a Herdr account. I don't need a Herdr account.
the product is not even to 1.0 yet and already the writing is on the wall for the path towards enshittification & acquisition by $bigco.
of course, I'm sure there will be some "usage without an account will still work" platitudes, but the trend of development is clearly going to be in the direction of features that "integrate" with the "developers using Herdr pay us money and/or we collect their data" business model.
The reason Herdr is novel, IMO, is its runtime owns the PTYs and builds a bidirectional messaging system on top of that. It’s like Pi’s RPC - a very limited version of it - which allows one to hook into agent i/o without needing to invoke “$agentcli -p”. There’s a lot they could build on that, and so I wonder why a managed cloud play was first on their list.
https://herdr.dev/blog/herdr-is-joining-y-combinator/
On the wall ? It's spray painted in big neon letters, and by themselves, lmao. Herdr cannot be trusted.
Now they have raised $6M in funding. [1]
Do not be surprised to realize that open source does not pay their bills.
[0] https://news.ycombinator.com/item?id=49201743
[1] https://herdr.dev/blog/herdr-raised-a-seed/