Claude Dispatch Setup: 1 Week In — Pairing Fix & Real Errors (2026)

On March 17, 2026, Anthropic rolled out Claude Dispatch — a way to send tasks from your smartphone directly to Claude Cowork running on your desktop. I jumped on it the day it launched and have been using it for about a week. The possibilities are genuinely exciting: being able to assign tasks to your PC from anywhere is undeniably useful.

📑Table of Contents

1. What Is Claude Dispatch? — Your Phone Becomes a Remote Control for Your PC
2. How to Set Up Dispatch — Step-by-Step Guide for 2026
3. What Can Dispatch Actually Do? — 5 Real Use Cases (2026)
4. Dispatch Not Working? Troubleshooting Guide
5. Security Considerations & Caveats
6. Pricing & Plan Requirements (March 2026)
7. My One-Week Review — What Actually Running It Taught Me
8. FAQ — Questions About Claude Dispatch (2026)
9. Final Thoughts — Dispatch Is the First Step Toward an AI Assistant in Your Pocket

That said, setup is still a pain point. I personally spent about an hour stuck on pairing before finding a workaround (more on that below). The overall stability leaves something to be desired, and you need to keep your PC powered on at all times, which isn’t ideal for everyone. It’s not quite at the “recommend it without caveats” stage yet. This guide combines the official documentation with my first-hand experience — setup, use cases, troubleshooting, and honest notes about what works and what doesn’t.

Item	Details
Feature overview	Send tasks to Cowork on your desktop from your phone, remotely
Release date	March 17, 2026 (research preview)
Supported plans	Max (available immediately) / Pro (rolling out shortly) / Free plan not yet supported
Supported OS	Desktop: macOS / Windows (x64)  |  Mobile: iOS / Android
Additional cost	None — included with your existing plan subscription
Setup time	~2 minutes

What Is Claude Dispatch? — Your Phone Becomes a Remote Control for Your PC

Claude Dispatch is a feature built into Claude Cowork that bridges your mobile device and desktop AI environment. The mental model is simple: your phone is the remote control, and your PC is the execution engine.

When you send a message via Dispatch on your phone, that instruction travels to Claude Cowork on your desktop, where it’s executed locally using your connected tools — file system, Slack, Google Drive, or whatever Connectors you’ve set up. The conversation thread is persistent and syncs across both devices, so you can monitor progress or follow up from either screen.

Key design decisions worth knowing:

• All processing happens on your PC — your files and data never leave your local environment to a remote cloud execution server
• Uses your existing Cowork setup — every Connector, plugin, and file permission you’ve already configured carries over
• One persistent thread — a single conversation syncs between phone and desktop, so context is never lost
• Permission gates — each action that involves writing, moving, or deleting files triggers a confirmation dialog on your desktop

Under the Hood — Tasks Are Auto-Routed to Claude Code or Cowork

Something the official docs make clear but most tutorials gloss over: when you send a task through Dispatch, Claude automatically decides where to run it. Development and coding work is routed to Claude Code; knowledge-work tasks run in Cowork. From the user’s perspective it all feels like “sending a Dispatch message,” but if you check the desktop sidebar you’ll see the session show up under either Claude Code or Cowork depending on the task type.

Another spec worth knowing upfront: Dispatch currently uses one continuous persistent thread. The official documentation lists this as a known limitation — you can’t create a new thread or manage multiple parallel threads yet. Every task lands in the same running conversation, which has a nice side effect (Claude carries context forward between tasks) but is a pain if you want to separate work streams by topic.

Dispatch also plugs into Claude’s Memory system. If you’ve told Claude things like “for this project, use this folder” or “always format output this way” in the past, those preferences carry through Dispatch sessions too. You can view, edit, or delete memory entries from Claude’s settings at any time, and you stay in full control of what gets remembered.

Dispatch is just one piece of Claude’s autonomous agent ecosystem. For a comprehensive comparison of all autonomous features — including Computer Use, Loop, and Channels — see Claude Can Now Control Your PC — Dispatch, Computer Use, Loop & Channels Explained.

How to Set Up Dispatch — Step-by-Step Guide for 2026

Setup takes roughly two minutes if both apps are already installed. Here’s the complete walkthrough.

Prerequisites — Install and Update Your Apps

Before you can pair, make sure everything is up to date:

1. Claude Desktop — download or update to the latest version from claude.com/download (macOS or Windows x64). Dispatch only appears in newer builds — if the menu is missing, the app version is almost certainly the culprit.
2. Claude Mobile App — update to the latest version on iOS (App Store) or Android (Google Play).
3. Same account on both — sign in with the same Claude account on both devices. Dispatch won’t work across different accounts.
4. Plan check — confirm you’re on Max or Pro. The Dispatch menu won’t appear on a Free plan account.

Pairing Process — QR Code Method

Once both apps are current:

1. Open Claude Desktop and click the Cowork tab in the sidebar.
2. In the left panel, click Dispatch.
3. Click “Get started” — you’ll be prompted to review file access permissions and sleep/wake settings. Enable the toggles.
4. A QR code will appear on screen.
5. Open the Claude mobile app on your phone, navigate to Cowork, and use the in-app scanner to scan the QR code.
6. Pairing completes in seconds. The same conversation thread will now appear on both devices.

Your First Test — Recommended Tasks for Verification

Don’t start with a complex, multi-step task. The safest way to verify Dispatch is working is to send a simple read-only information request first:

• “List all files in my Desktop folder” — tests file system access
• “What’s the latest message in the #general Slack channel?” — tests Connector access
• “Summarize the contents of [filename]” — tests file reading

Read-type tasks have roughly an 85% success rate in the current preview. Once those work, you can gradually escalate to more involved operations. Watch the desktop for any permission dialogs that need your approval — while you’re away from the screen, these can silently block task progress.

What Can Dispatch Actually Do? — 5 Real Use Cases (2026)

Here are five practical scenarios where Dispatch genuinely earns its keep:

Dispatch Not Working? Troubleshooting Guide

Because Dispatch is in research preview, issues are expected. Here’s a systematic breakdown of the most common problems and their fixes:

① Dispatch Menu Not Showing in Claude Desktop

② QR Code Pairing Fails

③ Tasks Stop Mid-Way (PC Goes to Sleep)

④ iOS App Freezes During Agent Execution (GitHub Issue #34059)

⑤ Low Task Success Rate — Too Many Failures

Security Considerations & Caveats

Giving your phone the ability to trigger file operations on your PC is a meaningful permission grant. Here’s what you should understand before fully committing:

• Code runs in a sandbox — executed code is isolated from your OS, reducing the risk of runaway processes
• Action confirmation dialogs — any operation involving writing, moving, or deleting files requires your explicit approval via a desktop dialog
• The catch with remote use: those dialogs appear on your desktop, not your phone. If you’re away from your PC, you won’t see them — tasks requiring confirmation will silently stall
• Only connect trusted Connectors — your Slack workspace, Google Drive, and other connected services become accessible through Dispatch. Review which Connectors are active before leaving tasks unattended

Dispatch vs. OpenClaw — How I Actually Split Them In Practice

I’ve been running both Claude Dispatch and OpenClaw in parallel, and they’ve settled into clearly different roles in my workflow. This isn’t a spec-sheet comparison — it’s how the two tools actually end up getting used day to day.

With that editorial out of the way, here’s how the two compare on the usual dimensions:

Aspect	Claude Dispatch	OpenClaw
Execution	Local (on your PC)	Cloud / configurable
Source	Closed (Anthropic)	Open source
Security posture	Sandboxed, confirmation gates	Prompt injection & config theft risks reported
Flexibility	Limited to Cowork ecosystem	100+ skills, Telegram/WhatsApp support
Best for	Users who prioritize data privacy	Power users who want maximum capability

If you’re handling sensitive business data and want the safer default, Dispatch wins. If you’re a developer or power user who wants broader integrations and doesn’t mind configuring security yourself, OpenClaw offers more headroom.

👉 Learn how Claude Cowork can automate your business workflows

Pricing & Plan Requirements (March 2026)

Dispatch itself costs nothing extra — it’s included as part of your existing subscription. The question is simply which plan you’re on:

Plan	Price (as of March 2026)	Dispatch Access
Max	$100–$200/month	✅ Available immediately
Pro	$20/month	✅ Rolling out within days of launch
Free	$0	⏳ Planned for H2 2026

There’s no separate Dispatch subscription, no usage metering for the feature itself, and no API key required. You just need an active Pro or Max plan and up-to-date apps.

👉 Claude Pro vs. Max — which plan is right for you? Full pricing breakdown
👉 Is Claude Max worth it? An honest look at the $100–$200/month plan

My One-Week Review — What Actually Running It Taught Me

So far this guide has mostly covered features and troubleshooting. This section is the part you won’t find in a spec sheet: what a week of actual use felt like, in plain terms.

The First Task I Sent Was a Simple Research Query — And It Worked

My first Dispatch task wasn’t planned out. I was away from my desk and just fired off a basic research question from my phone, the same way I’d normally chat with Claude. The response came back without any drama, and the latency felt essentially identical to running the same query sitting in front of my PC. Any worry I had about “remote means slower and clunkier” turned out to be misplaced.

Where It Genuinely Earned Its Keep

The moment that sold me on Dispatch wasn’t a big workflow — it was the small one. Throwing a quick task from my phone while I was out, letting it run in the background, and checking the result later. I didn’t have to go back to the PC. That’s it. It sounds boring, but the ability to offload a small task on impulse and have it done by the time I need it is genuinely useful in a way I didn’t expect.

Honest Verdict — I Haven’t Put It Into My Critical Workflow Yet

That said, I haven’t folded Dispatch into my business-critical workflow yet. The potential is clearly there, but the research-preview-era wobbles and the requirement to keep a PC running 24/7 make it feel more like “great for casual offloading” than “a core piece of infrastructure I’d bet my day on.” Try it, enjoy it, but don’t rip up your existing automations for it just yet.

The 24/7 PC Reality — Electricity, Heat, Noise

A question almost everyone asks: do you have to leave a PC on all the time? In my case, I already have a machine that runs 24/7 for other purposes, so Dispatch didn’t add a new “always on” cost for me. But I want to be honest about the rest: in summer, the electricity bill and the heat from an always-on PC are noticeable. The fan noise isn’t a real issue for me, but the running cost is worth thinking about before you commit to using Dispatch heavily.

My Fallback — VPN Into the Home Network

To cover the worst case — Dispatch showing “connected” when the PC is actually unreachable, or me being out and realizing the desktop app crashed — I keep a VPN tunnel to my home network as a backup. If something looks off, I can VPN in and poke at the machine directly. Leaning entirely on Dispatch without that fallback left me nervous; adding VPN + remote desktop as a safety net made me much more comfortable relying on it while out.

On macOS I Haven’t Hit the Big Bugs

I’ve been running Dispatch primarily on macOS, and across the one-week test I haven’t hit any freezes or crashes. The iOS “infinite loading spinner” bug (GitHub Issue #34059) that’s been reported online hasn’t shown up in my usage either. Other people are reporting instability, and I don’t want to dismiss that — it’s worth calibrating expectations to the reality that how Dispatch feels depends heavily on your OS, your apps, and how you use it. Don’t assume your experience will match anyone else’s review until you’ve tried it yourself.

FAQ — Questions About Claude Dispatch (2026)

1. Does Dispatch work on Windows?

Yes. Dispatch is supported on both macOS and Windows (x64). Download the latest Claude Desktop from claude.com/download and you’re set. Note that Windows ARM is not currently supported — only x64 builds.

2. Do my phone and PC need to be on the same Wi-Fi network?

No — this is one of Dispatch’s more useful design choices. Pairing and task execution sync over the internet, so your phone can be on a cellular network while your PC is on home Wi-Fi and everything still works. You don’t need to be on the same local network.

3. What happens if my PC goes to sleep while a task is running?

The task stops immediately. There’s no queuing, no task resume, and no partial save of progress. When you wake your PC and reopen Claude Desktop, the conversation thread will still be there, but the interrupted task needs to be sent again from scratch. Prevent this by disabling sleep on your PC before dispatching long-running tasks.

4. Will I get a notification when a task finishes?

Yes — according to Anthropic’s official documentation, Dispatch sends a push notification to your phone when a task is done or when Claude needs your go-ahead to continue. That’s the design spec.

Honest caveat: I’ve been running Dispatch primarily on macOS and haven’t exhaustively verified the push notification behavior on every mobile configuration. If you’re expecting notifications and not getting them, the most likely culprits are the Claude app’s notification permission, OS-level Do Not Disturb / Focus settings, or the app being in an unusual foreground state. Check those first before assuming notifications are broken.

5. OpenClaw or Dispatch — which should I use?

It depends on your priorities. If data security and simplicity matter most — especially if you handle confidential business files — Dispatch is the better choice: local execution, sandboxed, and backed by Anthropic’s infrastructure. If you want maximum flexibility, more integrations (Telegram, WhatsApp, 100+ skills), and are comfortable managing your own security config, OpenClaw offers more power. The two aren’t mutually exclusive; some power users run both for different workflows.

6. Do I need to re-pair my phone every time I use Dispatch?

No — pairing is a one-time setup. Once your phone and desktop are linked, that connection persists. You’ll only need to re-pair if you uninstall and reinstall one of the apps, sign out of your Claude account, or switch to a different device.

7. Can I use Dispatch on a free Claude plan?

Not yet. As of March 2026, Dispatch requires Pro ($20/month) or Max ($100–$200/month). Anthropic has indicated that free plan access is planned for the second half of 2026, but no specific date has been announced. If you’re on a free plan and eager to try it, upgrading to Pro is the current path.

8. Does Dispatch work on Claude Teams or Enterprise plans?

This has come up on Reddit: as of March 2026, enabling Dispatch on a Teams plan requires the admin to open Cowork’s admin settings through their own Claude Desktop instance and flip it on. Enterprise availability is handled individually through Anthropic, with no public rollout schedule. If you’re on a Teams or Enterprise plan and can’t see Dispatch, talk to your IT admin or your Anthropic account contact.

9. Can I cancel a running Dispatch task mid-execution?

Yes — the most reliable way is to stop the session on the PC side by opening Claude Desktop and halting the active Cowork or Claude Code session. Sending a “cancel” or “stop” message from your phone sometimes works too, but if the model is deep in a tool call, the PC-side stop is the guaranteed path. Remember that Dispatch uses a single persistent thread, so cancelling a task doesn’t wipe the conversation — your next instruction will land in the same thread.

10. How do I retrieve output files that Dispatch created?

Dispatch saves generated files to your PC’s filesystem by default, and the mobile app’s direct-download UI is currently limited. The cleanest workaround is to sync your Cowork workspace folder with a cloud storage provider like Google Drive. Files Claude creates on the desktop appear on your phone via Drive automatically, and you can share them from there without touching the PC.

11. Is “Claude Code Dispatch” (the Telegram one) the same as Cowork Dispatch?

No, they’re different things that keep getting confused in search results:

• Cowork Dispatch (the feature this guide covers): Anthropic’s official integration. Pairs the Claude mobile app with Claude Desktop and remotely drives Cowork or Claude Code sessions.
• Claude Code Dispatch: a relay layer — often third-party — that lets you control a local Claude Code instance from messaging apps like Telegram. Different purpose, different implementation, different source.

When you’re evaluating tutorials, check which one they’re actually about before following the setup steps.

12. How do I disable or unpair Dispatch?

Both the mobile and desktop apps have a Dispatch settings panel where you can remove individual paired devices. If you want to fully shut the feature off, toggle Dispatch off in Claude Desktop or delete the connection from your Cowork settings. If you ever need to lock things down urgently — a lost or stolen phone, for example — change your Claude account password and terminate all active sessions as well, to make sure nothing paired earlier can still reach your PC.

Final Thoughts — Dispatch Is the First Step Toward an AI Assistant in Your Pocket

Here’s where things stand in March 2026:

• What works well now: Information retrieval, file searches, Slack/email summaries — these run at ~85% success and are worth building into your workflow today
• What needs patience: Complex multi-step write operations hover around 50% success. The iOS freeze bug is real. Completion notifications don’t exist yet.
• Two things that prevent most issues: Keep both apps fully updated, and disable PC sleep before dispatching anything important
• The bigger picture: Dispatch is Cowork’s remote interface — it inherits everything you’ve already configured, which means the more you invest in your Cowork setup, the more you get out of Dispatch

If you’re already on Claude Pro or Max and use Cowork regularly, there’s no reason not to enable Dispatch today. Start with simple read tasks, get a feel for the reliability, and build up from there. The “AI assistant in your pocket” vision isn’t fully here yet — but with Dispatch, it’s closer than it’s ever been.

👉 Claude Cowork for business automation — full guide with real use cases
👉 Claude Code: CLI vs. Web vs. Desktop — which version should you use?