Use Claude Code from your phone, and know where the work runs.

Choose the route by where the code runs

Claude Code does not have a separate mobile app. From a phone you reach it through the Code tab in the Claude app, a chat app connected to a running session, a terminal app or a workspace such as TM8. Each route answers two questions differently: where does the code run, and does a computer need to stay on?

If your computer will be off, use a route that runs in the cloud. If the work needs your local files, tools or MCP servers, use a route that drives a session on your own machine, and keep that machine running.

• Cloud sessions: run on cloud infrastructure, so your computer can be off.
• Remote Control: drives a session on your computer from the Claude app or a browser.
• Channels: Telegram, Discord or iMessage messages reach a session that is already running.
• SSH: a terminal app on the phone connects to the computer that runs Claude Code.
• TM8: a WhatsApp request becomes work in a shared workspace.

Start cloud sessions from the Claude app

The Claude app for iOS and Android has a Code tab. From it you can start a cloud session: choose a GitHub repository and branch, describe the task and come back to it later. The session runs on cloud infrastructure, Anthropic-managed by default, so it keeps going after you put your phone away or close your laptop.

Cloud sessions need a claude.ai account; they are not reachable with an Anthropic Console API key or through a third-party provider such as Amazon Bedrock. If you do not see the Code tab, your plan or organization may not include these features.

• Runs: on cloud infrastructure.
• Needs: a claude.ai plan that includes Claude Code, and a repository on GitHub.
• Suits: tasks that should continue while your computer is off.

Continue a local session with Remote Control

Remote Control connects the Claude app, or claude.ai/code in any browser, to a Claude Code session running on your machine. Start it with claude remote-control, or run /remote-control in a session that is already open, then pick the session from the Code tab. Your files, tools and MCP servers stay local, and the session can send a push notification when a task finishes or needs a decision.

Remote Control is available on Pro, Max, Team and Enterprise plans. API keys are not supported, and on Team and Enterprise an Owner must first switch it on in the Claude Code admin settings. The computer has to stay on with the claude process running. The local session makes outbound HTTPS requests only and opens no inbound ports.

• Runs: on your computer.
• Needs: a claude.ai subscription sign-in, and the claude process kept running.
• Suits: work that needs your local files, tools or MCP servers.

Message a running session, or open a terminal over SSH

Channels push messages from a chat app into a Claude Code session that is already running, and Claude can reply in the same chat. Telegram, Discord and iMessage are included in the research preview. Each channel is a plugin that needs Bun, only senders on your allowlist can reach the session, and Team and Enterprise organizations must enable channels first.

Messages only arrive while the session is open. If Claude stops at a permission prompt while you are away, the session waits for you unless the channel can relay that prompt. WhatsApp is not one of the included channels; you would need to build your own channel or use a product that bridges WhatsApp. For full control, a terminal app on the phone can connect over SSH to the computer running Claude Code, with tmux keeping the session alive between connections, provided you have a secure way to reach that computer.

• Channels need: Bun, a bot or account for the chat app and an open session.
• SSH needs: network access to the computer, such as a VPN, and a terminal app.
• Both suit: quick checks and short instructions rather than long reviews.

Send work from WhatsApp to a shared workspace

TM8 takes a different route. You send a request from a connected WhatsApp conversation, and TM8 turns it into work in a shared workspace, where people coordinate Claude Code and Codex sessions that use their own logins, on a hosted seat or on their own machine or server. Updates come back to the conversation, and the task, the sessions and the result stay connected for review.

The recorded product tour shows a WhatsApp request and the summary that came back. It does not show a pull request being created, merged or deployed from WhatsApp. Consequential steps, such as an app change, wait for a person to approve them.

• Runs: on a hosted TM8 seat, or on your own machine or server.
• Needs: a TM8 workspace with a connected WhatsApp conversation.
• Suits: teams that want requests, sessions and review in one place.

Common questions