Claude on the go

Keep a Claude Code session going from the iPhone while you walk the dog. The app is Moshi, the desk command is walk, and the office Mac does the actual work. I stopped using Moshi in October 2026; this is the setup as it ran.

Kai Davis

I run a marketing consultancy and an SEO SaaS, and I build both with a stack of Claude Code sessions that write the tooling the next sessions run on.

bootstrapping.io · kaidavis.com · keywordmagic.ai · doubleyourecommerce.com

The one-line version. Start a session at the desk with walk <project> instead of cdc. On the walk, open Moshi, hit the Tmux tab, tap the session, and you are back in the live conversation. Nothing lost.

01What to do on the phone

Open Moshi, tap office. It moshes into the office Mac over the tailnet. The connection survives you switching from wifi to cell and your phone sleeping in a pocket.
Continuing a walk session? Open the Tmux tab, tap the session by name. You land inside the running conversation, exactly where it was.
Picking up any other project? Open the Recent tab, tap the folder. That gives you a fresh shell there, not the old chat, so type claude --resume and pick the conversation.
Walk off whenever. Close the app, lose signal, whatever. The session keeps running on the office Mac. Re-open and re-tap to drop back in.

02The two ways a chat comes back

Moshi shows you a folder and opens a shell in it. Whether the old conversation is sitting there waiting depends on how the session was started.

lossless Started with `walk`

Claude was running inside tmux the whole time, so the process never died. Moshi’s Tmux tab lists it; tap it and you are in the live session, mid-thought, full scrollback. This is the good one. Use walk for anything you might wander away from.

rebuilt A normal `cdc` session

Bare Claude, no tmux, so there is no live process to rejoin. Moshi opens a shell at the folder and you run claude --resume, which replays the conversation from its transcript. Slower, but it works from any shell.

03Starting a stroll-away session at the desk

Before you leave, launch it with walk. Same as cdc (worktree, account peg, model all included), but Claude runs in tmux so the phone can find it.

# at the desk, instead of `cdc kaibot`:
walk kaibot           # start a stroll-away session
walk km opus          # project + model, same as cdc
walk                  # list what is running right now

You can’t move an already-running cdc session into tmux after the fact, so decide at launch. Already left and forgot? Fall back to claude --resume from the Moshi shell.

04Command cheat-sheet

Where each command lives and what it does.
Command	Where	Does
`walk <project>`	desk	Start a session inside tmux so the phone can reattach. Shows up in Moshi’s Tmux tab.
`walk`	anywhere	List the tmux sessions currently running.
`kc`	phone / shell	List and attach tmux sessions by number. The fallback for non-Moshi clients (Blink, plain mosh). One session, it just attaches.
`claude --resume`	any shell	Rebuild a past conversation for the project you are standing in, from its transcript.

05The setup, for reference

This is already done. Here so future-you knows the moving parts.

Moshi Pro

The iPhone terminal built for coding agents. Mosh (survives roaming) and the tmux picker are Pro features. Currently on the $8/mo plan.

Tailnet + host

The phone reaches office at elkai@100.121.67.7 over Tailscale. The host is paired, so Moshi holds its own SSH key. Office stays awake, so a detached session survives.

A kaibot field note. The kit lives in ~/kaibot/scripts/mobile/ (see its README). walk loads from zsh/common.zsh; kc is a script in the kit.

You’ve reached the end of note 17 of 19

$400 1 hour

Book a call

A paid one-on-one call with answers to your questions about using AI for projects, building your AI stack, or growing your business with AI. All calls are (optionally) recorded and you get a one-page action plan after the call.

All nineteen field notes, in six chapters