I used ArchiveBox for years. It's really good. The self-hosting and maintenance gets annoying after a while though.
Link rot really bothers me and I want people to get into archiving web pages so that eventually there will be a decentralized mirror of the unslopped web sitting on people's hard-drives, ready to share whenever someone needs it. So, I made a worse version of ArchiveBox ( https://memoryhole.app ). My philosophy is that, if people see how it is easy to start archiving and how useful it is, then they'll keep it up with SingleFile, or ArchiveBox or anything else.
I switched to herdr this year after a decade of using tmux, and I haven't looked back since. Herdr is wonderful, not only because of the coding agent integrations, but also because it uses libghostty under the hood. So no terminal-emulator-inside-another-terminal-emulator shenanigans.
If you prefer GUIs, I can recommend herdr-gpui which connects to a herdr daemon. It has a bunch of goodies like remote phone pairing, and a built-in browser integration to send screenshots and notes to coding agents.
I've been using Zellij a long time and considered using Herdr, but the VC funding aspect scares me. I don't want to invest a bunch of time in a tool that's going to treat me as a product.
I used Zellij in the past, it is also fantastic and intuitive product. I had issues with... I think selection and copying and pasting which made me abandon it as I was getting frustrated. Herdr has been wonderful and I've been using it for a while.
Pretty much the first thing I tried to set up with I heard about Zellij and decided to give it a shot a while back was how to scroll back and copy paste text without using the mouse, since that's one of the core features of tmux for me. If my recollection is correct, the closest thing that I was able to figure out was some sort of built-in way to open output in a vim buffer, with the info I found when googling basically saying that it was intentionally not something the developers felt like it was important to implement anything closer to tmux for. Maybe it's changed since then but I distinctly got the impression that it using it would force me to adapt to a bunch of new workflows that didn't resemble anything I had seen before, and it didn't really seem worth the effort.
I don't know, this seems reasonable. I already know how to select, copy, and manipulate text in my $EDITOR. Why would a terminal multiplexer try to implement all of that rather than just let me open the terminal in my $EDITOR?
I'm not opposed to using the same shortcuts as editors (which is what tmux already does; you can even pick between emacs and vim shortcuts, in addition to configuring your own); there's just a lot of other stuff I _don't_ want from a text editor for my existing terminal output, like, editing text.
I recently switched to Zellij with Ghostty and the selection/copy/pasting seems to work just fine. I previously used zellij and kitty and I would have issues.
Same, but the cost of maintaining a fork fell through the floor in recent years. If a decent fork gains momentum, i can probably even stop spending tokens on mine.
But I’m already using ghostty. I installed herdr but made the mistake of launching it from within tmux and had no idea how to close it.
I then opened it somewhere else, but I had no idea how to interact with it. I also couldn’t get two other windows to “join” the same herdr session, so I gave up and went back to tmux.
For someone who has used screen / tmux for almost 30 years at this point, what does herdr do that tmux can’t?
I use Claude Code extensively. I also use plannotator extensively, which is how I found out about it.
It's all about agentic work. Tmux doesn't know what an Agent is. You use Pi, you use CC, you use Codex, ... they all have primary supports in Herdr with built-in integrations around each of these harnesses
But if you don't do any agentic work, Herdr has 0 value vs. tmux.
lol at the other replies waffling at you without describing the things that makes herdr appealing:
* agentic inbox [see which agents are waiting for your input/working/idle etc]
* agents can read, spawn, send-input etc other herdr panes
* makes cross harness orchestration / communication easier
fwiw I liked herdr initially but bounced after like a week because ghostty + notifications + harness extensions gave me enough that it wasnt worth learning the new thing.
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.
But Claude Code and Codex and the rest of tui harnesses are also very good at just typing in each other's panes basically when I need to send a message over. It's been working for almost a year now. I have been more intrigued by T3 code or something similar, just to be able for harnesses to message across machines.
overall not so much, but basically if inside tmux you have 100 terminals opened and only 10 of those has 'agents' it will allow you switch quickly between those 10 terminals without spending too much time on locating those. also it will show statuses about agents, is it work done already and you may need to check it and stuff like this.
I would assume other models have their own harnesses as well but I guess if you want it at all in one place that would make sense. I just need a single model.
The point about libghostty is that Herdr doesn't try to reimplement shell forwarding or emulation, instead it uses the same code your terminal already does. This avoids compatibility problems with more complex TUIs.
Running `herdr` always opens the same session, the app is a just a UI for a server running in the background. But there is no reason to open it in multiple windows, the point is to manage all shells from inside it.
Then you can from another machine do `herdr --remote xxx.local` (over Tailscale) to access the same session, or use `herdr machine add` to get your shells from all machines at once - I don't really use this part.
From someone who also used screen and tmux for 30 years: 3 reasons why I switched to herder. They may not be relevant to you and in that case tmux is just great. One: visual indication which agent is working and which is waiting for an input. Two: native support for remote herdr sessions - in the same view. Three: it’s responsive and can be completely touch-driven through menus on a small iOS screen in Termius.
I was looking into Herdr too, but could not bring myself to switch away from tmux yet (there are a couple of shortcuts that I have in my workflow, which I can't config in Herdr).
What I ended up doing was to use the tmux agent sidebar, which, with mouse support, I think does a lot of the same things already.
All of this, plus it knows what agent is running in which windows and what session that agent is working on. If you have to reboot, it can reconstruct all your terminal setup and restart the agents on the right session automatically.
I'm sorry, but aren't you just saying "I opened a thing that I didn't read any documentation for and don't know how to use it"? Did you know how to use tmux without reading the docs?
> Herdr is wonderful, not only because of the coding agent integrations, but also because it uses libghostty under the hood. So no terminal-emulator-inside-another-terminal-emulator shenanigans.
Now I’m interested. Does it have basic feature parity? How does it compare to tmux in your experience?
I was able to have a language model configure herdr with the same bindings that I was using in tmux.
It was a very easy transition from one to the other.
I started using it last week, the tui interface is very polished and it is mouse-friendly. It also allows you to configure the notification channels. Its a different beast from tmox, I'd say its quite more user-friendly and gives you a list of your running agents and their status directly on the interface.
I'm working on a small SaaS to archive web pages. It's still very early stage. So far there's a Chrome/Firefox extension and RSS feed reader. I'm still working on some more interesting integrations.
At the moment, it's not really a monetize-able product because it's so niche, and competitors are well established. My goal is to have stable, consistent pricing for years (hopefully decades), while also making it easy to switch to self-hosted alternatives.
I never thought anybody would pay for this. I have it locally, no need for sass. And it hits into my zettlekasten.
Even the people I know that have a use for this, are unwilling to pay and they rather suffer copy pasting things.
It seems more of a feature than a service imo so the integrations would be the interesting bit. Best of luck!!
"Not really monetizable yet" is usually a positioning problem, not a product one. Web archiving for everyone is hard to charge for. Web archiving for one group with a compliance or legal reason to keep pages (agencies, journalists, e-commerce teams tracking competitor prices) is very chargeable. Who's using it today?
I've been using another memory plugin [1] for the past couple months. Since this change, I almost never run session compaction. Instead, I opt to just make a new session, give the agent a task, and have it figure out what happened in previous session(s).
Decision summaries look really cool -- though the agent/model info probably won't be useful for me because I don't actually ever let agents commit code autonomously (even in branches).
Thanks! And I totally agree with your workflow, fresh sessions are the best way to avoid context degradation.
Just to clarify on the decision summaries - I actually don't let agents commit autonomously either! The summaries exist so that when you spin up that fresh session, the agent doesn't just read the code, it reads the context. It saves you from having to re-litigate past architectural decisions or re-explain your preferences every time you start a new task.
Nice tool you shared, feel free to mess around with engrim and provide feedback. You may end up really liking it. My Claude to Antigravity swaps have been really efficient and honestly, Antigravity has really upped their game lately so moving around for me personally this has been a big boost.
No big deal, I pay for zed plus/pro/max, whatever the subscription is called. I don’t miss any of the paid AI features when I switch laptops and can’t be bothered to login.
It’s a good editor, but the AI features are forgettable, and probably a distraction away from the core value proposition. They should sell commercial licenses like IntelliJ and be done with this AI monetization dilemma.
>But what if the “truth” is harder to find online because the infrastructure that once stored it is breaking down? Some of that is wear and tear. Link rot erases pages every day. Key sections of the United States Constitution briefly disappeared from the Library of Congress website because of a coding error.
This has bothered me for years. I think the solution lies in personal, private archives, and lending access to archived content within small communities.
This is not a complete picture. I use Zed daily and I have the AI features enabled, but I never use the built in agent in Zed. I reach for an agent in a separate terminal session.
Link rot really bothers me and I want people to get into archiving web pages so that eventually there will be a decentralized mirror of the unslopped web sitting on people's hard-drives, ready to share whenever someone needs it. So, I made a worse version of ArchiveBox ( https://memoryhole.app ). My philosophy is that, if people see how it is easy to start archiving and how useful it is, then they'll keep it up with SingleFile, or ArchiveBox or anything else.
reply