Theme 1 – Tmux as a stable base for agentic coding
Many commenters rely on tmux (or similar multiplexers) for its reliability and ease of integrating with Claude‑based agents.
“Tmux never crashes.” – oefrha
“I then open named tmux sessions, perform the ssh login via fingerprint, and then tell claude that he is free to take over that session with a given name.” – littlecranky67
“I am doing tmux + Claude but I wanted a bit more.” – petesergeant
Theme 2 – Herdr offers integrated features but suffers from crashes
Herdr is praised for providing an all‑in‑one agentic environment, yet its instability drives users to fall back on tmux or nest tmux inside Herdr.
“Herdr does it all so much better out of the box when it comes to agentic coding.” – thomas_witt
“My only problem with herdr is its propensity to randomly crash and take out the whole session…. Tmux never crashes.” – oefrha
“I still run sessions and processes I really don’t want to lose inside tmux, nested inside herdr.” – oefrha
Theme 3 – Custom or daemon‑oriented alternatives for better persistence and control
Several users have built or are experimenting with their own multiplexers, daemon‑based agents, or remote‑control setups to avoid the limitations of existing tools.
“I created my own “terminal multiplexer for AI agents” after trying out herdr…. My own tool, Jai, connects to multiple machines, handles multiple agents and enables agent to agent communication.” – michaelanckaert
“Like others here I created my own terminal multiplexer as well…. Daemon that holds all sessions… thin client mode… wasm responsive webui…”. – zackham
“Isn’t this the wrong architecture? Fundamentally, a coding agent should be running as a headless/detached process, a daemon.” – teiferer
“You can just install Claude Code on the server and drive it from Claude Desktop via remote control.” – blfr