← Back to blog

Claude Code on Phone: Apps vs Dispatch

Updated 2026-11: how people run claude code on phone with apps, a browser terminal, and Dispatch, not official Remote Control.

12 min read

Claude Code on Phone: Apps vs Dispatch

Updated 2026-11

TL;DR: There is no single official "Claude Code phone app." People run Claude Code on phone in a few different ways: a mobile app that gives you a cloud machine and a chat or terminal, a chat layer that turns local Claude Code sessions into bots you control from the phone, a browser tab that is the terminal, Dispatch that texts a desktop Cowork session, or a cloud coding agent you can steer — even by voice — after you close the laptop. These are not the same product as official Remote Control, where the phone is only a window into a session that already lives on your computer.

A mobile app demo for running Claude Code from a phone

A mobile app built so you can use Claude Code from the phone without leaving the laptop on. Source: an X walkthrough recorded in August 2026.

Why "on your phone" means more than one setup

"Claude Code on phone" is not one product. It is a mix of at least 3 setups people used in 2026: a mobile app that gives you a cloud machine, a chat layer that talks to a local Claude Code session, and Dispatch, which is a walkie-talkie to a desktop Cowork session. Official Remote Control is a fourth path, and it already has its own write-up at Claude Code remote control. This article is about the other setups, when you want to kick off a task, add to a running task, or ship something from a phone, without treating every app as the same window into a local session.

A mobile app that runs Claude Code without the laptop on

One path is a dedicated mobile app. In an August 2026 walkthrough, a builder on vacation said they had never shipped so much, even though they didn't use their computer at all. The app, Yado, is a mobile app to use Claude Code or Codex right from your phone without needing your laptop on. You connect your accounts, you get a cloud machine, and you get coding with AI with your own subscription. You can use a chat interface or a terminal one. You can connect your CLIs and MCP and tweak some settings.

The same walkthrough does a little demo from the phone: build Galaga, an arcade game kind of like Space Invaders, just one level, end to end, then ship it and reply with a test link. The point is not the game. The caption is the useful part: a mobile app to use Claude Code and Codex on your phone, without ever touching your laptop, and it is not another remote control for your laptop. You just get coding with AI with your own subscription. That is the difference you should look for in any Claude Code on phone app: do you get a cloud machine and start coding without needing your laptop on, or is the phone only attaching to a computer you already left on?

Turn local Claude Code into a bot you can message

A chat layer is a second path that keeps Claude Code on the machines you already use, then lets the phone talk to those sessions. A November 2026 demo describes Codync as a way to turn Claude Code, Codex, and 40+ AI agents into bots you can control from your phone. It connects your locally installed AI agents to a chat interface, so you can manage coding tasks remotely.

The network piece is built so each computer decides who may write to its agents. Cloud assistants in the same account can message those bots. In the demo, one request is simply: have Reviewer on your laptop check PR #42. The reply comes back: Reviewer approved PR #42. No blockers. You are not retyping the whole repo on a small screen. You are sending a short instruction to a session that already has the repo, the tools, and the context.

This is closer to a walkie-talkie than to an IDE. Agent Tailscale in the same demo is set up as one invite per computer, no ports, no VPN, direct, peer to peer, end-to-end encrypted. When there's no direct path, public relays. Direct when it can, through a shared relay otherwise. Private, direct only, on the same network. Each computer decides who may write to its agents. Treat the phone as the place you give the next instruction, not as the place the code lives.

A browser tab that is the terminal

A browser terminal is a third path in November 2025, and it does not need a special Claude Code app at all. If you can run CLI agents in the browser, any phone browser can open the same session with 1 click to a project. A walkthrough of a universal CLI agent server puts it this way: you can launch any CLI apps and agents just like visiting a website. Each session is a browser tab, which means you can multitask with a general purpose web terminal engine. If something runs in a terminal, it runs on the web automatically. And since these are just web pages, you can access them from any browser.

Three ways to run Claude Code from a phone

Three common setups: a mobile app with the laptop off, a chat layer to a local agent, and Dispatch to a desktop that stays on.

That setup also sends desktop push notifications for CLI apps and CLI agents. You can kick off an agent task and forget about it. They will message you when done, regardless of which CLI app. An instant launcher lets you kick off an agent with a specific project with one click: enter what you want to build and select an agent. For "Claude Code on phone," this is the path that feels like opening a tab, not installing a new IDE.

Dispatch is a walkie-talkie to the desktop, not Remote Control

A lot of "done from the phone" videos are actually about Claude Dispatch. A March 2026 walkthrough talks about what Dispatch is, how it works, and how it is different from remote control — many people are confused on it — then shows the setup and a couple of examples live from the phone. That is still a real way to run work from a phone, but it is not the same as official Remote Control, and it is not the same as a Claude Code app.

A walkthrough of Claude Dispatch from a phone

Dispatch is set up as a persistent conversation between the desktop Cowork session and the phone. Source: an X walkthrough from March 2026.

Laptop off versus a desktop that must stay on

In 2026 the practical split is this: a cloud machine can keep running after you close the laptop, while Dispatch needs the desktop awake.

A March 2026 walkthrough says it plainly: Dispatch is a way for you to control your Claude Cowork through your mobile phone.

You can think of it like a walkie talkie to your co-work session running on your desktop.

For that, your desktop needs to be on, and the Claude desktop app needs to be on. What you get is a single persistent conversation between your desktop and your phone. If you give it a task on Monday, it will remember it on Tuesday and Thursday. It has full context of everything you have talked about. Claude has access to everything on your desktop — connectors, files, browsers, plugins — and everything is controllable through your phone. So it's basically like you're texting your AI worker and it's doing its work on your machine while you're out grabbing a cup of coffee.

The same walkthrough also flags a setup detail people miss: once you have the updated apps, you need to ensure the Keep Computer Awake setting is turned on, under Settings, then General. If the desktop sleeps, the walkie-talkie goes quiet.

A later demo makes the "from the phone" part concrete. You can be connected to Claude Desktop and also connected to Claude from your phone, plus a data tool through MCP. You ask a question on the phone — how many orders last month — and Dispatch routes it as a task. Cowork uses the MCP server and comes back with a number, then you can ask whether that is better or worse than last month, still from the phone. You could be driving to work and asking questions, and Claude is using the tools on the computer to give you results. That is Dispatch: the computer stays the worker, the phone stays the message.

Cloud agents you can steer after you close the laptop

A cloud coding agent is a related pattern in 2026: you kick the task off in the cloud, which means you can close the laptop and the task still runs. You can pick that task back up whenever you want because it's running in the cloud. You can even use your phone. You can just add to the running task without interrupting. Voice works the same way. You can pop in your headphones, go for a walk, kick off a voice session, and it will run and let you know when it's done.

The idea shows up when a spark of an idea might show up away from the desk. You want to be ready and let it build while you do the other tasks. A chat-based onboarding flow can take the repos you want and research what the environment might need for setup. Once you have a named environment, you can kick off new tasks from wherever you are, including the phone. This is closer to Yado's "laptop off" model than to Dispatch's "desktop must stay awake" model. When you pick a Claude Code on phone setup, ask which of those two constraints you are signing up for.

Check a phone result with Pachat

A phone is a good place to kick off a task or add to a running task, and a bad place to blindly accept the result. If you just asked, from the phone, how many orders you had last month, and the answer came back through an MCP server, you still want a second pass before you ship a decision. Pachat is a web product at pachat.ai, described on the site as "Different personal AI agents, in one group chat." Put your Claude, Grok Bot, Muse and ChatGPT dots in one group chat. They check each other's facts and argue it out, then you make the call. You can open it in the phone's browser and paste the draft or the answer you just got on the go. For a closer look at that group setup, see the AI group chat guide. Dispatch details are also in Claude Cowork Dispatch.

Pachat homepage, where you start a group with several AI agents

The Pachat homepage. You can open it in a phone browser and start a group with several agents.

Agents checking each other's work in a Pachat group

In the group, agents can check a draft or a number before you accept it.

A sign-off step where you make the final call

The last step stays with you, even when the work started from a phone.

FAQ

Is there an official Claude Code phone app?

Not as a single store app that replaces the desktop CLI. In 2026, what people use instead are mobile apps that give you a cloud machine and a chat or terminal, chat layers that talk to local Claude Code sessions, browser terminals you can open on a phone, Dispatch to a desktop Cowork session, or cloud coding agents you can steer after the laptop is closed.

Is Dispatch the same as Remote Control?

No. Dispatch is a walkie-talkie to a Cowork session running on your desktop. A March 2026 walkthrough says the desktop and the Claude desktop app need to stay on, and you get a persistent conversation with the same context across days. Official Remote Control is a window into a local session. A dedicated mobile app that gives you its own cloud machine is a third thing: the laptop can be off.

Can I run Claude Code from a browser on my phone?

Yes, if you run the CLI in a web terminal. A November 2025 walkthrough of a universal CLI agent server shows Claude Code and other agents launched as browser tabs, which you can open from any browser, including a phone browser. You can kick off a task and get a notification when it is done, and an instant launcher can start an agent on a specific project with 1 click. That is not a special Claude Code app. It is the same terminal, opened as a page.

What if I only want to send a short instruction?

Use a chat layer that turns local Claude Code sessions into bots on the phone, or Dispatch if the worker should stay on your desktop. A November 2026 demo sends a short request — have the reviewer on the laptop check PR #42 — and reads the reply. You are not trying to edit the whole repo on a small screen.

Should I accept work that started on a phone without a second look?

No. Start the task from the phone if you want, then put the draft or the answer in a Pachat group so more than one agent can check it. In a April 2026 demo, a number came back from an MCP server after a question asked on the phone; that is useful, and it is still worth a second pass before you ship a decision. You still make the call. Start at pachat.ai.

How is this different from official Remote Control?

Official Remote Control, covered in a separate 2026-11 article, is a window into a local session that already lives on your computer. The 3 setups in this article are different. A mobile app can give you a cloud machine so the laptop is off. A chat layer talks to locally installed agents. Dispatch is a walkie-talkie to a Cowork session and needs the desktop awake, as a March 2026 walkthrough shows. See Claude Code remote control if that window-into-the-session path is the one you want.

Ready to put different AIs in one group chat? Start at pachat.ai.

References

  • @mehdigatbache, 2026-08-19: https://x.com/mehdigatbache/status/2089980239103320415
  • @soggycuitsog, 2026-11-16: https://x.com/soggycuitsog/status/2122250443908665452
  • @nidhisinghattri, 2026-03-19: https://x.com/nidhisinghattri/status/2034651063979286664
  • @heffhq, 2026-04-30: https://x.com/heffhq/status/2049560315667587363
  • @cocktailpeanut, 2025-11-06: https://x.com/cocktailpeanut/status/1986103926924390576
  • @openaidevs, 2026-09-30: https://x.com/openaidevs/status/2104997734294139151
  • Pachat: https://pachat.ai/

More from the blog

All articles →

Start with the decision in front of you.