Yes — three third-party apps and Anthropic's own Remote Control feature let you monitor and control Claude Code from your phone today. OpenAI shipping Codex Mobile on May 14, 2026 confirms this is now a mainstream category, not a niche workaround. Here is how each option works and how to pick the right one for your setup.

TL;DR: As of May 2026, you have four real options for Claude Code on your phone: (1) Claude Code Remote Control (Anthropic's built-in, ships in v2.1.79+), (2) Grass (agent-agnostic cloud VM with iOS app, sessions survive a closed laptop), (3) Happy Coder (Claude-specific, claims E2EE), and (4) DIY SSH+tmux. Each has specific named limitations documented below.

The Four Options for Claude Code on Your Phone

Here are the working options as of May 2026, in order from lowest-friction to most control:

1. Claude Code Remote Control — Anthropic's built-in feature (v2.1.79+, released Feb 25, 2026). Run claude remote-control or /rc in your terminal, scan a QR code with the Claude iOS or Android app, and pick up the session from your phone. Push notifications added April 28, 2026 (v2.1.110). No third-party install required.

2. Grass — An agent-agnostic cloud VM with a native iOS app. Your agent runs on a Daytona-powered cloud VM, so sessions survive a closed or sleeping laptop. Supports Claude Code, Codex, and Open Code. Two tiers: cloud VM at codeongrass.com (10 free hours, no credit card), and a local CLI (npm install -g @grass-ai/ide) for WiFi-connected setups.

3. Happy Coder (also called Happier) — A Claude Code–specific mobile client with claimed end-to-end encryption via TweetNaCl. Open-source, 29+ contributors active as of May 2026. Note: archived sub-repos (happy-cli, happy-server) were folded into the monorepo Feb 14, 2026 — the project is not abandoned despite how it looks.

4. DIY SSH + tmux + Tailscale — Raw terminal access via apps like Termius. Full control, no third-party relay, no additional accounts. High setup cost; SSH connections drop when switching from WiFi to cellular.

Why This Category Exists Now

OpenAI shipped Codex Mobile on May 14, 2026 — built into the ChatGPT app for iOS and Android. Their announcement framed it directly: "From your phone, you can work across all of your threads, review outputs, approve commands, change models, or start something new." That validates the user need industry-wide. The core need is not a terminal on your phone — it is four specific things: check on long-running tasks, approve or reject changes mid-session, kick off new work from anywhere, and keep sessions alive without being at a desk.

Anthropic made the same read in February 2026. Their launch tweet for Remote Control read: "Kick off a task in your terminal and pick it up from your phone while you take a walk or join a meeting. Claude keeps running on your machine."

Decision Guide: Which Option Fits Your Setup?

Use Claude Code Remote Control if...

• You already have Claude Code v2.1.79+ and the Claude iOS/Android app
• You want zero additional installs
• You are comfortable with the limitations below

Named limitations of Remote Control:

• Session dies when laptop sleeps or lid closes — the agent runs on your local machine, not in the cloud. This is the most-cited limitation on Reddit.
• Cannot start new sessions from mobile — you must already have a session running on your desktop before picking it up on your phone.
• QR code required every time — no persistent pairing, even for daily-use projects.
• No per-project isolation — developers running 3-4 repos find context-switching messy.
• iOS native app bug (GitHub #45539, April 2026) — sessions fail to start in the native iOS app. Workaround: use claude.ai web on your phone instead of the native app.
• Encryption: TLS only, not end-to-end — Anthropic's documentation is explicit about this. Only chat messages and tool results flow through the bridge; files stay on your local machine.

Remote Control is a solid remote viewer for an existing session. It is not a mobile-first workflow, and it does not solve the laptop-tether problem.

Use Grass if...

• You want sessions to survive a closed or sleeping laptop
• You run more than one coding agent (Claude Code, Codex, Open Code)
• You want to kick off new work from your phone, not just monitor existing sessions
• You prefer BYOK — your API keys stay on your machine or in your cloud VM, never handled by a third party

Named limitations of Grass:

• The cloud VM free tier is 10 hours; paid tiers required for sustained use.
• The local CLI (@grass-ai/ide) requires your laptop to stay on — only the cloud VM product (codeongrass.com) gives you true always-on behavior.
• No authentication on the local server — recommended for trusted networks or Tailscale. Anyone who can reach the port can interact with your agent.

The differentiator no other option in this comparison matches: sessions survive a closed laptop. When you run on the Grass cloud VM, your agent keeps running on Daytona infrastructure whether your MacBook is open, asleep, or shut down. Grass is also the only agent-agnostic option in this list — Claude Code, Codex, and Open Code are all first-class citizens.

Use Happy Coder if...

• You want Claude Code–specific mobile access with claimed E2EE
• You are comfortable evaluating security claims without a public audit
• You want an active open-source project with community contributors

Named limitations of Happy Coder:

• Claude Code only — does not support Codex or Open Code.
• No public security audit — the E2EE claim uses TweetNaCl (same library as Signal), but there is no published SECURITY.md or third-party audit as of May 2026.
• Archived sub-repos cause false abandonment signals — check the main monorepo, not the archived happy-cli/happy-server repos, for activity.

Use DIY SSH + tmux if...

• You need full terminal control with no relay
• You already have Tailscale or a trusted VPN
• You are comfortable with mobile SSH apps (Termius, Blink)

Named limitation: SSH connections drop when switching from WiFi to cellular — the most-cited deal-breaker in r/vibecoding and r/ClaudeCode threads. One user: "SSH seemed like the obvious solution. Connection would drop when I switched from WiFi to cellular. After 2 weeks I just gave up on it."

Comparison Table

Security Note: siteboon/claudecodeui

If you are researching older recommendations, note that siteboon/claudecodeui (8.2k GitHub stars, widely recommended in 2025) had three critical CVEs published in March 2026: remote code execution via WebSocket, shell injection, and command injection. Articles written before March 2026 recommending it are linking to unpatched software. Do not use it.

FAQ

Is there an official Claude Code mobile app from Anthropic?

There is no standalone Claude Code iOS or Android app from Anthropic. Anthropic launched Claude Code as a research preview on iOS on October 20, 2025 — for monitoring tasks and reviewing code — but not for starting local terminal sessions from mobile. The official mobile access path today is Claude Code Remote Control (v2.1.79+, released Feb 25, 2026), which requires the Claude iOS or Android app.

Does Claude Code have a mobile app?

Claude Code does not have its own dedicated mobile app. The three practical ways to reach Claude Code from your phone in 2026 are: (1) Anthropic's Remote Control feature built into the Claude app, (2) third-party mobile clients like Grass or Happy Coder, and (3) SSH+tmux via a mobile terminal app.

Can I use Claude Code from my phone without keeping my laptop on?

Yes, but only with Grass's cloud VM product. Every other option — Remote Control, Happy Coder, the local Grass CLI, and SSH — requires your laptop or server to stay running. Grass runs your agent on a Daytona cloud VM, so the session continues whether your laptop is open, asleep, or shut down.

Is Claude Code Remote Control end-to-end encrypted?

No. Anthropic's documentation explicitly states that Remote Control uses TLS encryption, not end-to-end encryption. Only chat messages and tool results flow through the encrypted bridge; your files and environment variables stay on your local machine. Happy Coder claims E2EE via TweetNaCl but has no published security audit as of May 2026.

How is Codex Mobile different from Claude Code mobile access?

OpenAI's Codex Mobile (launched May 14, 2026, inside the ChatGPT app for iOS and Android) controls Codex agents only — it does not give you access to Claude Code. Grass is currently the only option that supports both Claude Code and Codex from a single mobile interface, plus Open Code.

What is the best way to access Claude Code on iPhone in 2026?

It depends on your constraint. For zero setup, use Remote Control — but expect the iOS native app bug (use claude.ai web as the workaround). For sessions that survive a closed laptop, use Grass cloud VM. For Claude-specific mobile access with community E2EE support, try Happy Coder. For full terminal control with no relay, use Termius + Tailscale + tmux.

What This Looks Like in Practice

Morning commute scenario: You want to kick off a refactoring task before you reach the office.

• Remote Control: cannot start new sessions from mobile. Not possible.
• Grass: open the iOS app, select your repo, send the task. Agent starts on the cloud VM. You arrive at your desk with the work already underway.
• Happy Coder: possible if you have an existing session or can start one.

Overnight run scenario: You want an agent to work on a large codebase task while you sleep.

• Remote Control: session dies when your laptop sleeps. Not viable without keeping your machine on all night.
• Grass cloud VM: agent keeps running. Check progress from your phone in the morning.
• DIY SSH+tmux: viable if your laptop or server stays on; SSH drop on cellular is not a concern if you check from home WiFi.