Async Mobile Dev: Six Claude Agents from a Phone
The author runs six Claude Code agents on a Tailscale-only Vultr VM, controlled entirely from an iPhone using Termius, mosh, and tmux. A PreToolUse hook posts AskUserQuestion prompts to a Poke webhook, sending push notifications that enable asynchronous, interruption-friendly development. Git worktrees, deterministic port allocation, and cost- and security-conscious VM operations make the setup fast, parallel, and safe.
Key Points
- On-demand, Tailscale-only Vultr VM (no public SSH) provides a secure, pay-per-use dev box controlled from an iPhone.
- Mosh plus tmux delivers resilient, persistent terminal sessions suited to mobile usage; agent forwarding limitation is handled by falling back to SSH inside tmux for GitHub ops.
- Push notifications via a Claude PreToolUse hook and Poke webhook alert the user when Claude needs input, enabling true async development.
- Parallel work via Git worktrees and per-branch deterministic port mapping lets six Claude Code agents run simultaneously without conflicts.
- A permissive but isolated trust model with tight cost bounds makes the setup safe and economical for iterative development.
Sentiment
The community is predominantly positive about the technical innovation and shares genuine excitement about mobile AI-assisted development workflows, but this enthusiasm is tempered by significant concern about broader implications. The work-life balance thread resonated deeply, suggesting many developers feel anxious about the always-on trajectory these tools enable. The discussion is constructive rather than hostile, with thoughtful debate on both sides, though the labor politics sub-threads became heated. Overall, Hacker News agrees the approach works technically but is divided on whether it represents progress or a troubling shift in developer expectations.
In Agreement
- Running multiple Claude Code sessions from a phone is a genuine productivity multiplier, enabling async development during otherwise idle moments like walking the dog or waiting in line.
- Git worktrees combined with AI agents allow developers to work on multiple features simultaneously, turning a single developer into a small team.
- The async notification pattern — kick off work, pocket the phone, get buzzed when the agent needs input — transforms downtime into productive development without requiring constant screen time.
- This workflow is already being adopted by well-known developers who review AI-generated code exclusively through PRs rather than watching the agent work in real time.
- The disposable VM approach with Tailscale-only access provides a reasonable security model for running permissive AI agents, isolating them from production credentials.
Opposed
- Always-on AI coding tools will create an expectation of constant productivity, eroding work-life boundaries as employers compare workers who code from their phones against those who don't.
- When AI generates code that developers no longer read or understand, it creates a black-box maintenance problem — the codebase becomes as opaque as compiled binary data.
- Quality software development requires focused desk time with proper screen real estate and deep attention, not short bursts of phone-based interaction.
- The productivity claims around AI coding agents are overhyped and may represent coordinated marketing rather than genuine capability improvements.
- This workflow only works for small personal projects; large enterprise codebases still choke the best models, making the approach impractical for day-job work.
- Relying on AI to write all code leads to cognitive atrophy — developers should maintain their problem-solving skills rather than outsourcing everything to an LLM.