# Claude Dispatch: The AI That Keeps Working When You Don't > Source: > Published: 2026-05-25 13:41:08+00:00 # Claude Dispatch: The AI That Keeps Working When You Don't ### Anthropic launched a remote control for desktop AI. The success rate is 50/50. You should still use it. Your timeline is flooded with “game-changing” AI announcements. Easy to tune them out. But the most useful thing [Anthropic](https://www.anthropic.com/) shipped this year is not a reasoning breakthrough. It is a QR code. Enter **Claude Dispatch:** It does one thing: turns your phone into a remote control for your desktop. Text it from the couch, *“pull last month’s receipts into a spreadsheet,”* put the phone down, walk off. By the time you open the laptop, the work is done. Since its quiet launch in March, the verdict is clear. It is clunky. It fails half the time. And it is still brilliant. Here is what the viral launch posts leave out: how Dispatch actually fits into a real workflow 📢 *A quick word before we get into it.* Dispatch only pays off if you can actually drive Claude. Most people own the tool and use 10% of it. That is the gap ** Outskill** closes: Their mentors compressed 800+ hours of Claude practice into a[ 16-hour live workshop](https://links.outskill.com/AIC1R): Chat, Cowork, Code, plus Skills and Connectors to automate your desktop, and vibe coding apps with zero code. 🧠 Saturday & Sunday: [Master Claude](https://links.outskill.com/AIC1R) this weekend. Get it working while you sleep. Exactly like Dispatch. **Table of Contents** 1. It’s Not a Mobile AI. It’s a Remote Control. 2. How to Set it Up in Two Minutes 3. What Works and What Doesn’t 4. The Workflows Worth Building 5. Limitations, Security and How It Compares 6. What This Actually Signals ## 1. It’s Not a Mobile AI. It’s a Remote Control. The biggest **misconception** about Dispatch is baked into how people describe it. ‘**AI on your phone**.’ ‘** Mobile Claude**.’ Neither is accurate. Dispatch is a **walkie-talkie**. Your phone sends the message. Your Mac does the work. **The architecture that changes everything** The [processing happens on your desktop](https://support.claude.com/en/articles/13947068-assign-tasks-from-anywhere-in-claude-cowork). **Always**. When you type ‘**compile a report from last quarter’s sales data**‘ on your iPhone at dinner, that instruction travels through Anthropic’s relay to the **Claude Desktop app** running on your computer. Claude then **reads** your actual local files, uses your configured connectors, executes the task in the sandbox and sends the result back to your phone. Your phone does **zero** **AI processing**. Not a byte. This matters for **two reasons**. First, your **data** never leaves your machine for processing. The files you’re analyzing, the emails you’re summarizing, [the code you’re reviewing all stays ](https://www.the-ai-corner.com/p/the-claude-code-system-that-replaces)** local**. Second, everything you’ve already set up in **Cowork**, your Notion connector, your Google Drive, your custom plugins works through Dispatch **automatically**. No **reconfiguration**. No **new setup**. You point your **phone** at the desktop session that’s already running. **Stop waiting. Start delegating.** Regular Claude chat is **synchronous**. You prompt, Claude responds, you read, you prompt again. The loop is **fast** and requires your **active** **attention** throughout. Dispatch is asynchronous. You assign, walk away, return to results. The **value** isn’t in a better answer. It’s in the time you reclaim between the instruction and the output. Think about what that means in **practice**. Before Dispatch, if you were commuting and remembered you needed a performance report for a 9 AM meeting, you had two options: **scramble** in the morning or **cut** your evening short. With Dispatch, you **pull** out your phone on the train and type ‘pull Q1 sales data from the spreadsheet in /projects and **generate **a formatted performance report.’ You put your phone in your **pocket**. The report is on your desktop when you get home. *Dispatch is about doing work, not answering questions. The category transition is from AI as a responsive tool to AI as an autonomous worker operating within a defined scope while you do other things.* **2. How to Set it Up in Two Minutes** If you’ve seen AI tools that promise ‘quick setup’ and then require Docker, environment variables and an afternoon on Stack Overflow, Dispatch is the **antidote**. The setup is genuinely **fast** and I say that as someone who has sat through a lot of painful AI tool **onboarding**. **What you need** The best part is that you [only need three things:](https://www.productcompass.pm/p/claude-dispatch-guide?hide_intro_popup=true) The **Claude Desktop** app on macOS or Windows (updated to the latest version)The **Claude mobile app** on your iPhone or AndroidEither a **Claude Max** or**Pro** subscription. Max subscribers got access on March 17. Pro followed within days. The price difference is significant since Max runs $100-200 per month, Pro is $20. **Both** work for Dispatch. **The actual steps** **Open** Claude Desktop, go to the Cowork tab, click the new Dispatch option. A **QR code** appears. Open Claude on your phone, scan it. Done. A ‘Dispatch’ entry appears in your mobile sidebar and the same conversation is now mirrored on both devices. Two things to do immediately after pairing: enable ‘**keep desktop awake’** in Dispatch settings so your Mac doesn’t sleep mid-task and grant file access permissions when prompted. If you skip that second step, Dispatch will ask for it the first time you try to access a local folder, which is **disorienting **when you’re on a commute with a task already in progress. **3. What Works and What Doesn’t** The **honest **version: Dispatch has roughly a **50/50 success rate** on complex tasks. That sounds bad. **It isn’t**, because the **50%** that works covers most of what you’ll actually want to use it for. **What reliably works** File searches are **solid**. [Ask Dispatch](https://findskill.ai/blog/claude-dispatch-remote-cowork/) to find a **specific PDF**, locate screenshots containing certain words, or surface a document you know is somewhere in** /downloads**, it finds them. Email and Notion summaries work well through their **connectors**. ‘Summarize my most recent emails and flag anything urgent’ comes back fast and accurately. Adding content to connected apps, a URL to a Notion database, an item to a task list also works without** issues**. **Browser automation** got significantly more powerful when Computer Use launched on March 23, a week after Dispatch. The combination is genuinely **different** in kind. From your **phone**: ‘go to YouTube, find the 20 most recent videos about [Claude Cowork](https://www.the-ai-corner.com/p/10-claude-cowork-workflows-that-actually), analyze the top comments for common questions.’ Dispatch opens Chrome on your desktop, navigates to YouTube, scrolls through comments, compiles the report. **What doesn’t work yet** Opening apps directly on your **Mac** fails. Sending files via **iMessage** fails. Accessing **Safari** tabs through **AppleScript **doesn’t work. Some connectors throw **authorization errors** even when correctly configured in Cowork. Todoist was a reported example at launch. Bottom line is that **terminal access** isn’t there yet. **Long-running complex** tasks fail silently more often than they should. The most **frustrating** pattern: Dispatch shows ‘seen’ on your message but never responds, while your usage still ticks up. If you’re running a **20-minute** research task and it fails at **minute 18** without telling you, that’s a **real problem**. Start with **simple,** **single-purpose** tasks. Earn **trust **before you chain steps. **4. The Workflows Worth Building:** ## Keep reading with a 7-day free trial Subscribe to The AI Corner to keep reading this post and get 7 days of free access to the full post archives.