Claude mobile apps
The iOS and Android apps — an assistant in their own right, and the place you check on work that Claude Code or Cowork is doing elsewhere.
Last verified August 21, 2026 · 3 sources
The mobile apps do the obvious thing — Claude, on a phone — and one much less obvious thing: they are a control surface for work happening somewhere else.
Checking on work you started elsewhere
| Route | What it does |
|---|---|
| Claude Code on the web | Runs in the mobile app; start a long task and check back |
| Remote Control | Drive a session running on your own machine, from your phone |
| Dispatch | Message a task from your phone; open the Desktop session it creates |
claude --teleport |
Pull a session started on mobile into your terminal |
| Cowork | Start a task at your desk, check on it from your phone (beta on mobile) |
The pattern across all of these: the phone is rarely where the work happens, and often where you decide whether it is going well. For tasks measured in hours, that is the difference between delegating and babysitting.
What it does not do
- No local file access in the sense the desktop app has. A phone is not where Claude Science or desktop scheduled tasks run.
- Handoffs to claude.ai require a subscription.
What this page does not claim
Per-platform differences between the iOS and Android builds, and minimum OS versions, are not documented here.
Plan availability
Anything left blank is not documented publicly, not a claim that it is unavailable. Compare every feature at once in the availability matrix.
- FreeIncluded
- ProIncluded
- MaxIncluded
- TeamIncluded
- EnterpriseIncluded
- APINot available
Sources
- 01Claude Code on mobileOfficialcode.claude.com
- 02Claude Code overviewOfficialcode.claude.comDocuments Remote Control, Dispatch and claude --teleport as the session-portability routes.
- 03Claude Cowork on web and mobileOfficialclaude.com
Page changelog
- VerifiedSession-portability routes re-checked against the Claude Code surface table.