semanticly you're right. But saying I exposed the browser chrome of the chromium headless browser is rather confusing. Edge, Arc, etc all call themselves browsers even when they don't build the rendering engine.
fully graphical - can run over ssh. So you can connect to a remote server and actually see what a browser session from that machine is viewing. Also helpful if you're running an agent that produces html or PRs, it can then preview it in the terminal for your visual review rather than bumping out to another application.
Lastly - driving or doing a PR or regression test - I've found that having claude in chrome drive my browser takes over the UX for me as the human, using this keeps coding sessions away from my real broser.
I’m working on a side project to rebuild OBS-like tools with a focus on an agentic workflow. Currently testing at https://arclightlive.com if anyone wants to try.
Take an open model and put it on chip, it becomes a dedicated sub-agent. You can still use a frontier model to check things or orchestrate but having 1000 sub-agents becomes very possible. I was already long AMD but just added to my position.
It's built for ai agents, tmux works but isn't designed for an ai workflow. Herdr is also very well thought out, not just the design/approach but also the interaction and mouse support, responsive support, etc. I had been using tmux, switched and haven't looked back.
> It's built for ai agents, tmux works but isn't designed for an ai workflow
So an opportunity to learn the Bitter Lesson [1].
If tmux is good enough for people today, it should be good enough for agets tomorrow. That gap might comprise a beachhead. But you'd better scramble off the shores onto something more defensible fast.
You say this like there's no value in a transitional technology. Yes, tmux should be good enough for agents tomorrow. But here we are, today.
Also, herdr is just an open source project with no VC capital behind it. So I don't think it needs to scramble to something more defensible. It can live a happy life pleasing users and then fade into obsolescence.
> Yes, tmux should be good enough for agents tomorrow. But here we are, today.
tmux is good enough for agents today. they're great at driving it, they're great at customizing it, what's the problem people have with it? i am confused.
I'm sorry but I am still confused. What specifically does herdr give me over tmux? "It is designed for agents" is just marketing speech, it means nothing. Ok, it has mouse support, fine, I don't care about that one but I can see how it's useful to some people. That has nothing to do with agents though. zellij also has a better user experience than tmux, so you could just use that or any of the other dozen multiplexers.
I understand it has the agent pane on the left that tells you what is running but... that's it?
Realistically, what I use about its agent stuff is:
- reliable notification pings either via what your terminal app uses (e.g., ghostty's) or system or just within herdr only
- if absolutely necessary, be able to tell agent sessions to observe and run commands on a herdr pane (security beware, for obvious reasons)
- herdr --remote which is basically a quick SSH -> attach to herdr on a remote
- prefix+g (equivalent to prefix+w in tmux) presents itself nicer, has binds for agent state filtering and its /search imho is mildly nicer than tmux's
Arguably, you can have the same points in others if you know how to configure tmux or zellij already, so if you're comfortable with that then you really don't have to use herdr.
There is a cross platform terminal notification cli that I used to vibe code notifications in like 5minutes and I have traffic light indicators on my tmux panes showing when an agent is waiting. The other things are also all possible. An agent is super happy to remote control tmux, it knows all the commands!
Yep, I did similar stuff too! Used something like ntfy to push notifs to an Android or just whatever commands are available on the OS you're in (e.g., `notify-send`). And for state reads herdr has `herdr pane read` while you can happily accomplish similar results with `tmux capture-pane` or similar.
IME yes that’s basically it. Other features haven’t really been significant value add for me. Some of the keybindings are different in minor ways. It has some mouse support but I have found that it doesn’t work well with certain apps/selections (eg: less).
It’s fine.
When running many agents something like the “idle/working workstreams” gutter is honestly helpful though.
Cool project, love the visuals. Wish it would merge as a plugin or something to a project like http://ghostty.org/ while I appreciate the visual fun, there are other pragmatic tools beyond visuals that are handy.
I think the best thing that could happen would be to be able to add shaders to windows in Wayland.
When MacOS 9 was a thing, I had an extension called “out of context menus” that added options such as “Gaussian blur” the the context menus so you could blur a window.
It can only apply shader(s) to the current frame I think. To produce the crt ghosting you'd probably need access to the previous frame (not an expert).
I've tried the shaders in the following repo with ghostty. They definitely work. I ended up keeping a cursor trail shader. https://github.com/0xhckr/ghostty-shaders
Yes, correct! If you check out https://ghostty.org/docs/config/reference, the iPreviousCursor is available, so it can be used against the iCurrentCursor to produce a fading effect. But I think the entire previous framebuffer isn't there (yet).
reply