When should you use it?
- Your coding tasks run for many minutes without needing you
- You want to use gaps in the day instead of desk time
- You can keep the dev machine isolated from production
Not for: Machines holding production secrets; Teams whose policy forbids permissive agent modes
What do you need, and what do you get?
You need
- A cloud VM you can start and stop
- Tailscale, a mobile SSH client, mosh and tmux
- A push notification service that accepts webhooks
You get
- Persistent agent sessions you can resume from the phone
- A phone alert containing the agent's question
- Parallel features each in its own worktree
How does it work, step by step?
- Lock down accessGive the VM no public SSH listener; reach it only over the private network, with a firewall as backup.
- Make sessions surviveUse mosh for the connection and auto-attach to tmux on login so closing the app loses nothing.
- Wire up alertsAdd a hook that fires when the agent asks a question and sends the text to your phone.
- Split work by worktreeGive each feature branch its own worktree, window and port so agents do not collide.
- Bound the blast radiusKeep the VM disposable and pay-per-use so a runaway session is cheap and contained.
The prompt
Our own prompt, inspired by mgranda and written to work in Claude Code. Values in lime are placeholders.
Set up a development VM I can drive from my phone. Requirements: reachable only over my Tailscale network, firewall closed to everything else; login drops me into a persistent tmux session; create a hook so that whenever you need input from me, the question text is posted to [push webhook URL]; one git worktree and tmux window per feature branch with non-clashing ports. Give me start and stop scripts. Do not put any production credentials on this machine.
Inspired by mgranda: Claude Code On-The-Go. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Mosh does not forward your SSH agent, so git pushes needing auth may need plain SSH.
- Permissive mode is only sensible because the VM holds nothing important.
Our take
The phone is not the clever part of mgranda's setup; the question hook is. People who try mobile agent work usually give up because they keep opening a terminal that has nothing new in it, whereas a push alert carrying the agent's actual question turns it into a proper asynchronous loop. You answer when asked and otherwise get on with your day. The infrastructure choices are sound. Keeping SSH off the public internet behind Tailscale removes the most common attack path, mosh and tmux stop flaky mobile connections from killing sessions, and worktrees give each feature an isolated copy of the code so six agents do not trample each other. The trust model is the boundary to copy before the convenience: permissive mode runs only on a disposable machine with no production credentials, so the worst outcome is a broken VM. Shut the VM down when idle since billing is hourly, keep push messages free of secrets, and review diffs on a larger screen before merging anything important.
Where the time goes back: Waiting time disappears: a task that takes the agent a quarter of an hour no longer holds you at a desk.
FAQ
Why notifications rather than checking in?
How was the setup built?
Source and credit
Inspired by mgranda. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Claude Code On-The-Go
- Creator
- mgranda
- Published on
- granda.org
- Original date
- Jan 2, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.