threecheese

They did just announce that final wall though.

In its current incarnation, superlogical is exactly the same as the new herdr, with the same gaps. A TUI does not appear in their backlog either. They are a native app.

Not the new one though. I'm sure it'll come. The new herdr is not backwards compatible, and the TUI is unlikely to see development (at least in its current form).

I was actually kinda pissed when i realized this. Then i got an invite to Rex from superlogical, and I was free! Only to find out it's the same damn thing :)

Heeler has a PR open to target the new core, but no sign anyone is working on a tui for it :(

Right now the new herdr has more ... just more. Rex has the polish, attention to detail, and attention to performance.

They both follow the same "gui with a cli to manage the engine which owns the PTYs, has some interaction protocol, wraps coding agent interfaces, and you can connect to remote machines" model.

Unfortunately they are both GUI only atm and so I'm still using herdr-tui over ssh until it breaks or we get a tui surface.

I love the current model, where I can use the tui in ghosttty or wezterm or iterm, or pop an ssh session, and if it makes sense there's a gui version for whatever device I'm using. It's like magic, I'm free to do whatever from wherever. Forcing a GUI feels like them asserting ownership or control. Now I need their mobile app if i want to develop remotely, etc. I recognize the irony, the core is open- I'm free to develop against it - but we all know that realistically only a handful will and those will lag. Also i am sure that GUI is first because that's where the users are. Eh.

I'm on your side wrt sensitive data, but there are other use cases. I use the OpenAI one: Dot, and this is why I've found it valuable:

- it uses a very fast model for normal responses, but also does reasoning and all the agent things. It responds within a second or two. - it feels like it has multiple threads internally- it can respond to your messages and questions immediately, but also do thinking and web search like a normal thread. - it can communicate with other agent threads, as an orchestrator (although this isn't unique to it). - it has dedicated persistent compute already, with a desktop that you control, and so gives you a UI surface area that the agent can use.

And so the value for me is an always-on agent conversation, where you can tell it to perform tasks and ask it questions, and it just does all of it immediately. Those tasks can be software development instead of like ordering dinner.

It has SMS / phone comm channels also, but I don't use that.

If tmux can know what an agent is, it can be leveraged to communicate with an instance of that agent (input and output) given it owns the PTY, and that terminal output can be structured somehow.

If it can communicate with the agent, it can be used to drive the agent - to send it tasks, and communicate the status of those tasks.

And so Herdr - and Superlogical, and others, is a tool which leverages PTY ownership and terminal protocols to allow orchestration of coding agents across vendors using their CLI surfaces.

The agents learned to communicate this way.

Either:

1. the training data contained samples demonstrating how to do this, or it was post trained into the model intentionally; 2. the training data contained enough predicate knowledge that they could reason through it themselves, or; 3. they invented a novel approach using their vast intelligence (/s).

These are in order of likelihood. Given the high probability that it was (1), can't we just ... not do that? Does the frontier model need to be as good at recipes as offensive cybersecurity?

You aren't wrong, but this AI thing which we're trying to give people:

1. is something that many intensely don't want, and many with valid reasons; 2. will inarguably consume some of a resource which we all need, which is already becoming more scarce globally; 3. is in many cases contributing negatively to actual or perceived quality of life via DC noise and pollution; 4. threatens the livelihood of millions in the near term, even if it will improve outcomes over time; 5. is inextricably tied to and will substantially benefit a wealthy cohort, who is already seen as exerting undue control over populations governments ; 6. present potential systemic societal risk, yet is moving forward at breakneck speed; 7. has apparent total US government support, despite complaints about all the above, in a political environment which is frankly frightening, and where that government is exercising little restraint against - and collecting more sensitive data than ever about - citizens who protest against policy.

None of us should be surprised about this reaction.

SpaceX-stans (god i can't believe i just typed that) use it, there's a whole subculture grokking (heinlein is turning in his grave) their way towards the same vibe coded nonsense as the rest of us.

Tbh I think Thariq or one of the others passively hinted/suggested but didn't come out and make a categorical statement. I've seen anecdotal evidence of folks getting those extra data messages in various "not using the official harness" scenarios, but there's way more people like you who are not having issues.

If you say you wrote it, I'll read it. I commit to this.

We can all throw questions like this at our LLMs, and the objections you'll see here revolve around having our time wasted by folks who believe their LLM output is an accomplishment; we're getting sick of it.

Specs-as-history is rapidly becoming an antipattern as teams actually try to scale SDD. We're already putting guardrails in agents.md (non-normative in all caps), some teams are actually offboarding them - to Rally (which I find the height of hilarity).

Spec docs - at least in all the other things like this thing - aren't a living representation of truth, instead they are a collection of snapshots in time of feature deliverables. Layer 500 of these on top of each other and they quickly become not just useless but actively harmful. Archive them, compile them, whatever your plugin does, it still doesn't help. Nobody is going to pay for tokens just to keep the specs time-coherent, when the agent can just read the code.

Don't get me wrong, a spec is a useful bit of kit for development, just like Jira and Rally, but also like Jira and Rally they aren't the source of truth because there's already a better one which you just paid for.

One thing I've noticed is a lot more HF assets require personal information collection to download. Not sure if that's new corporate compliance or an attempt to manage bandwidth (or a marketing channel).