Maude vs an SSH app and tmux
Termius, Blink or Prompt with tmux already gets Claude Code onto your phone, for free. The question is whether a 100-column TUI driven through a soft keyboard is something you want to use twice.
If you already run Claude Code on a server, you can reach it from your phone today without buying anything. Install an SSH client — Termius, Blink Shell, Prompt, or a-Shell — attach to a tmux session, and there it is. Plenty of people work exactly this way and are happy.
This page is not going to pretend that setup is broken. It is not. It is the reference implementation, and Maude exists because of what it feels like on the twentieth use rather than the first.
What the DIY setup gets right
- It is free beyond the SSH client, and several good ones cost nothing.
- It is complete. You get the actual terminal, so every slash command, every TUI panel, every prompt behaves exactly as it does on your desktop. Nothing is missing because nobody had to reimplement it.
- tmux makes sessions durable. Detach, lose signal, come back, reattach — the session is still there.
- It generalises. The same app tails logs, restarts services and edits files. It is not single-purpose.
If that is working for you, there is a decent argument for leaving it alone.
What starts to hurt
The friction is not any single blocking problem. It is a pile of small ones, all downstream of the same fact: Claude Code's interface is a full-screen terminal UI designed for a keyboard and a wide window, and a phone is neither.
- Reflow. A TUI draws to a fixed grid. On a narrow screen, tables, diffs and box-drawing wrap into confetti. Rotating to landscape helps and costs you half the visible lines.
- The keyboard. Ctrl, Esc and arrow keys live behind a modifier bar. Claude Code's interactive prompts — permission dialogs, the model picker, question pickers — are arrow-key driven, so every decision becomes a small game of hunt-the-key.
- Escape sequences. Double-Esc, Ctrl-C and Ctrl-B collide with tmux's own prefix and with the SSH client's gesture handling. Sooner or later you detach a session you meant to interrupt.
- Scrollback. Reading back through a long tool-use run in a tmux copy-mode buffer with touch scrolling is genuinely unpleasant.
- No notifications. A terminal cannot tell you it finished. You either sit and watch it or keep reopening the app to check.
- Reconnect cost. Every time iOS suspends the app you re-dial SSH, re-attach tmux, and find your place again.
What a purpose-built client changes
Maude connects the same way — SSH to your box, Claude Code running there — but renders the session as an app instead of a terminal. Messages are markdown. Tool calls are collapsible cards, so a 400-line file read is one line until you want it. Slash commands that would be TUI panels become native sheets: /model is a picker, /mcp is a management screen, /compact is a progress bar. Sessions live in a daemon on the server, so closing the app is not a disconnection, and when a task finishes you get a push notification.
| SSH app + tmux | Maude | |
|---|---|---|
| Cost | Free (most clients) | $2.99/week or $59.99/year |
| Connection | SSH | SSH |
| Rendering | Terminal grid, reflows badly | Native mobile layout |
| Tool output | Inline, unbounded | Collapsible cards |
| Interactive prompts | Arrow-key TUI | Native buttons and sheets |
| Push when finished | No | Yes |
| Survives app suspension | Reattach to tmux manually | Reconnects to the session |
| General server admin | Yes — it is a real shell | No, Claude Code only |
| Full slash-command coverage | Everything, exactly as on desktop | The mobile-relevant subset |
Stay with SSH and tmux if you also need a real shell on that box, if you use slash commands Maude has not wrapped, or if the friction genuinely does not bother you. It is free and it is complete — those are strong arguments.
Switch to Maude if the phone is a place you actually work rather than somewhere you occasionally check on a run, and the interface is what keeps sending you back to the laptop.
They coexist fine
Nothing about Maude stops you keeping an SSH client on the same server — it is an ordinary SSH connection to an ordinary machine. Most people who switch keep a terminal app around for the times they need a shell rather than an agent. Use whichever fits the moment.
