Don't change your terminal workflow — put four parallel coding agents on your phone exactly as they are
remobi.app: Don't change your terminal workflow for mobile · Connor Adams
9 min total·Actually worth watching closely: ~4 min·3 must-watch clips
- 0:00 – 1:00Listen
Why you keep wanting to check
Opens on the real itch: once your agents are running and you step away from the machine, you get this compulsion to check on them — are they working well, do they need steering, do they need you?
The real motivation for mobile monitoring isn't working on the go; it's the nagging need to know whether the agent needs a human right now.
Pure spoken setup — the speaker is just talking, nothing on screen. Audio is enough.▶ Jump to 0:00Speaker · Connor Adams - 1:00 – 2:25Skim
Picking apart the existing options
Runs through Happy, the built-in mobile handoff, and generic terminal apps for your phone, pinning each one's catch: works with Claude Code only, a relay server he isn't sure he trusts, a handoff you have to press yourself, SSH key management and touch controls.
What they all share is that they ask you to bend your existing workflow to fit the product, rather than the other way round.
The slide is a static list of product names and bullet points; a glance while listening gets you each rejection — no need to watch frame by frame.▶ Jump to 1:00Speaker · Connor Adams - 2:25 – 3:30Watch
Agents running side by side
A live look at the day-to-day workflow with T-Mux as a window manager: the screen split into four panes with a coding agent in each, and one custom key command that brings the whole set of sessions up at once.
T-Mux's role here is window manager for your terminal, which turns watching several agents at once into a one-screen affair.
All the information lives in the screen layout — how many panes, what's running in each, what happens when the key command fires. Audio alone loses it completely. There's also a status line along the bottom the speaker himself admits is hard to read, so you need to be looking.▶ Jump to 2:25Speaker · Connor Adams - 3:30 – 5:00Watch
AI writes the config, a human reads the diff
The speaker admits the whole complicated setup was vibed and that he doesn't really need to know T-Mux; then he demos lazygit and critique for looking at what the agents changed.
The bar for this workflow is down to just having a vision in your head — but the human review before you commit is the step you don't skip.
The review part is a live demo — you see how the terminal UI tools page through changes and how fast a pass goes. That rhythm is the value of this stretch.▶ Jump to 3:30Speaker · Connor Adams - 5:00 – 6:30Watch
The same session, moved onto your phone
Introduces and demos Rimobi: a progressive web app that works on iOS and Android, connects to the server running on his own machine, and brings that exact terminal session onto the phone — shift-tab into plan mode, a button for Git, gesture scrolling, double-tap to zoom into a pane.
It isn't a remade mobile product; it's the terminal session you already have, projected onto the phone untouched.
Whether a terminal is workable on a touchscreen is something only your eyes can judge — how scrolling tracks your finger, how a pane zooms on double-tap, how the buttons respond. None of that survives in text.▶ Jump to 5:00Speaker · Connor Adams - 6:30 – 7:50Listen
Don't put your terminal on the public internet
Spells out that the phone and the dev machine have to talk over a private tunnel — TailScale by default, or Cloudflare Tunnels or ngrok — and gives the install path: the skill and the NPM package set T-Mux up for you if you haven't got it, log you straight into the session, and turn an existing config into key bindings for the touchscreen mode.
Expose a remote terminal service like this straight to the public internet and you've pwned your own computer.
Spoken security warning and install steps; nothing new is happening on screen. Catching the three tunnel options and that one warning is enough.▶ Jump to 6:30Speaker · Connor Adams - 7:50 – 9:03Listen
Q&A: why roll your own workflow
Answers questions from the floor on the trade-off against off-the-shelf products like Conductor, and on why a remote dev machine plus a pure terminal is a portable setup — you connect from any device and get exactly the same environment, part of why he left VS Code.
While the tooling is still at the fuck around and find out stage, owning and refining your own workflow is worth more in the long run than adopting a finished product.
Straight question and answer from the stage, no demo alongside it. The points are worth hearing; the picture doesn't matter.▶ Jump to 7:50Speaker · Connor Adams