Why doesn't dotMux support mosh?

Because of how mosh works, not because we haven’t got to it. mosh runs a terminal emulator on the server and sends your device a picture of the screen — a grid of characters and colors — instead of the raw stream of bytes your programs actually write.

That grid is a ceiling. Anything mosh’s server-side emulator doesn’t model never leaves the server, so no client can put it back: inline images are the obvious casualty, and newer terminal features are at its mercy. dotMux renders with Ghostty precisely so that modern TUIs and AI coding agents look right, and a mosh connection would quietly undo that on exactly those sessions.

So this one is a standard rather than a gap: we won’t ship a connection mode that silently downgrades your terminal. Surviving a dropped connection is a separate problem, and dotMux approaches it from the server side instead: with tmux or herdr, your work keeps running while you’re away, and reconnecting reattaches you to it rather than dropping you into a fresh shell.

The word doing the work there is silently. herdr has the same kind of ceiling, and dotMux supports it anyway, because it isn’t slipped in between you and your shell: herdr is a multiplexer you run on your own server and pick per host, the way you pick tmux, and the app lists what it costs where you pick it. mosh would have been dotMux’s choice, made for you on every session it carried — so mosh stays out.