A browser-accessible tmux setup that surfaces terminals waiting on input instead of making me hunt for them
I keep ending up with a pile of long-running terminal sessions: deploys, log tails, migrations, and lately a bunch of Claude Code runs. The annoying part isn’t starting them, it’s figuring out which tab/session actually needs me.
This was useful because it treats terminals as persistent sessions and adds a simple “needs action” layer on top, so the ones blocked on input/approval float up instead of getting lost in the pile. Under the hood it’s basically ttyd + tmux, but wrapped in a way that makes reopening from a browser/desktop/phone less janky than my usual setup.
A couple things I liked:
- sessions survive browser closes and reconnects cleanly
- grid view is handy when you want to watch multiple jobs at once
- descriptions are auto-generated, which is nicer than trying to remember what
dev-7was doing - sharing a session for pair debugging is less painful than screen sharing a terminal
Mostly posting because this feels relevant to the “too many terminals, not enough attention” problem.
This software's code is partially AI-generated.
u/lymn — 3 hours ago