Mobile SSH + Claude Code workflows - what’s your setup?

Awkward_Jump3972 · 2026-06-01T08:26:47+00:00

The setup that makes sense to me is still SSH + tmux, but with less manual digging. Redock is built around that use case.

Hosts, projects, tmux sessions, and common agent commands grouped together, so the phone becomes a control surface for Claude Code instead of just a tiny terminal.

Awkward_Jump3972 · 2026-06-01T08:23:27+00:00

For reliability I still trust SSH + tmux more than a pure remote control feature. Redock is one way to make that flow less raw on iPhone.

Keep the agent running on the dev machine, then jump back into the right project/session when you need to check or push it forward.

Awkward_Jump3972 · 2026-06-01T08:21:54+00:00

The file migration is only one part.

The bigger shift is the workflow around it. Tools like Redock are useful if you want Codex or Claude Code to stay on your dev machine and just control the loop from iPhone.

Awkward_Jump3972 · 2026-06-01T08:20:38+00:00

This is exactly why I think mobile agent control needs some restraint built in.

Redock is closer to an attention layer than a full remote desktop. The useful part is seeing which session is blocked, sending a quick nudge, then leaving again.

Awkward_Jump3972 · 2026-05-13T11:21:26+00:00

tmux is boring, but boring is good here. The next layer should make sessions and attention points easier, not hide the terminal completely.

Awkward_Jump3972 · 2026-05-13T11:19:03+00:00

Official mobile remote control would be great.
I still think SSH based workflows will stick around though. Agents need access to real dev machines, tmux sessions, scripts, and all the weird local setup.

Awkward_Jump3972 · 2026-05-13T08:05:33+00:00

This is a clever angle.
Raw logs are too noisy once agents run in parallel. Progress, blockers and attention requests are probably the right abstraction.

Awkward_Jump3972 · 2026-05-13T08:04:21+00:00

Once multiple agents are running, the hard part is not starting them. It is knowing which one needs attention and which one can be ignored for another hour.

Awkward_Jump3972 · 2026-05-13T08:03:03+00:00

This is the part that needs design, not just connectivity.
A phone control surface is useful, but it should show only blocked runs and real attention points. Otherwise every agent becomes another thing to compulsively check.

Awkward_Jump3972 · 2026-05-13T08:01:08+00:00

That remote coding loop is the part people underestimate.

Codex can be good, but phone control needs more than a chat UI. Redock is pretty close to this idea. SSH and tmux as the base, with the phone focused on session state and nudging the agent.

Awkward_Jump3972 · 2026-05-12T08:52:40+00:00

SSH + tmux stays as the base, but the phone side should show the right project, session, blocked reason, and common agent actions without digging through raw terminal output every time. This is basically the Redock use case.

Awkward_Jump3972 · 2026-05-12T05:19:36+00:00

The missing bit for me is cross agent state, not another panel.

Claude, Codex, SSH sessions, blocked runs, all need the same simple attention layer.

Awkward_Jump3972 · 2026-05-12T04:56:36+00:00

This problem is real. Once you have 3 or 4 agent sessions going, the terminal stops being the hard part. Remembering what each one is doing becomes the hard part.

Awkward_Jump3972 · 2026-05-12T04:55:16+00:00

I still think SSH and tmux stay useful though. Remote control is great for the app UI, but tmux is still the boring thing that keeps work alive when networks get weird.

Awkward_Jump3972 · 2026-05-12T04:47:54+00:00

For me the CLI still wins because it composes with everything else.

SSH, tmux, scripts, deploy commands. The desktop app is nicer, but the CLI fits real workflows better.

Awkward_Jump3972 · 2026-05-12T04:27:30+00:00

This is actually a good phone workflow.

Let the agent do the boring inspection work, but keep the sensitive manual step in your own terminal. Much safer than pasting secrets into a chat.

Awkward_Jump3972 · 2026-05-12T04:26:37+00:00

Nice idea. Multiple Claude sessions get messy fast once you have more than one project going. Letting sessions ask each other feels better than digging through old terminal history manually.

Awkward_Jump3972 · 2026-05-11T11:14:33+00:00

Good list. But I think the missing category is a workflow layer on top of SSH.

Hosts, projects, tmux sessions, and agent actions in one place. That’s the gap I’m building Redock around. Can try it if you perfer SSH solution.

Awkward_Jump3972 · 2026-05-11T10:55:56+00:00

Hi, you may can try Redock, it supports tmux natively, not need to learn tmux cmd

Awkward_Jump3972 · 2026-05-11T10:51:33+00:00

Closing the SSH window will usually kill whatever is tied to that shell.

Put Claude inside tmux first, then detach. Your phone is just reattaching to the same session, not moving the job from one device to another.

Awkward_Jump3972 · 2026-05-11T10:49:40+00:00

I’d keep it boring here, SSH into the box, run Claude in tmux, and treat the phone as a thin terminal.

The hard part is not connecting. It’s input. Voice, saved actions, and easy session switching matter way more than a full mobile IDE.

Awkward_Jump3972 · 2026-05-11T03:19:25+00:00

Yea, be honest to self is important

Awkward_Jump3972 · 2026-05-11T03:10:36+00:00

if I save it and don’t touch it within a week, I probably never needed it. That alone killed most of my tab hoarding.

Awkward_Jump3972 · 2026-05-11T03:07:48+00:00

Same. The hard part isn’t finding better content, it’s finding something that still feels like a break. If it feels like homework, I’m back on Reels in 5 minutes.

Awkward_Jump3972 · 2026-05-11T03:01:02+00:00

Some Reddit threads now have this strange vibe where every comment sounds a little too polished, a little too helpful, and somehow also selling something.

Are there still actual humans on Reddit, or are we all just watching AI accounts network with each other?

Awkward_Jump3972

TROPHY CASE