5 ms·
I found both Tmux and Herdr to be insufferable, but they work for many people. I'm not in the business of managing 17 agents at the same time (I have 1 to 4 age
by arw0n 23d ago
I found both Tmux and Herdr to be insufferable, but they work for many people. I'm not in the business of managing 17 agents at the same time (I have 1 to 4 agents I manage, those might have sub-agents, but I'm not a micro-manager). The hand-off problem itself is trivial, it is a txt file that needs to be sent around, but I haven't seen any good tools giving good UX for it yet.
1. Means running somewhere that is not your computer. I just use my personal server for this.
2. Should probably be done in the repo. Just add the context file in a dedicated sub directory. At this point I think these kinds of artefacts are part of the SE process, and fair to check into source control.
3. Can be done by letting the TUI write/draft emails via MCP.
4. Can be done with something like OpenCode or PiCode, which just allows you to switch in their TUI interface. Beware though, context has to be re-ingested, so it costs a couple of cents.
But again, in the end context is just a file. By switching models, you are paying the price of not having any context cached, but for manual steps that's usually not super relevant. Just be careful about adding these kinds of things to automated workflows, as a cost like 25c can add up when agents run amok.