How to Set Up Claude Dispatch to Control Cowork From Your Phone

Mar 22, 2026

I was away from my desk when I needed Claude to search through my project files. I could have used remote desktop, but that’s slow and clunky. Then I discovered Claude Dispatch - a feature that lets me send tasks from my phone to run on my desktop. Here’s how I set it up and what actually works.

The Problem

I wanted to use Claude while away from my computer. Specifically:

Look up information from local files
Search documents I don’t have synced to cloud
Prepare research for when I return to my desk

Remote desktop solutions felt like overkill. I didn’t need to see my screen - I just needed Claude to do work on my behalf.

What Claude Dispatch Actually Does

Claude Dispatch creates a bridge between your Claude mobile app and Claude Desktop. When you send a task from your phone, it executes on your desktop computer. Results sync back to both devices.

This is part of the Cowork feature suite - Anthropic’s approach to letting Claude work with your local files and applications.

The architecture looks like this:

+------------------+          Cloud           +------------------+
|  Claude Mobile   | <----------------------> |  Claude Servers  |
|      (Phone)     |                          +------------------+
+----------------+--|                                   |
                   |                                   |
            QR Code Scan                          Task Queue
                   |                                   |
                   v                                   v
          +------------------+                 +------------------+
          |  Claude Desktop  | <---------------|  Your Computer   |
          |  (Computer)      |   Execute Task  |  Local Files     |
          +------------------+                 +------------------+

Both devices need internet connectivity. The sync happens through Claude’s cloud infrastructure - no local network required.

The Setup Process

I expected a complex configuration. API keys, config files, maybe port forwarding. But the actual setup took about two minutes.

Prerequisites

Claude Desktop installed and running
Claude mobile app (iOS or Android)
Both devices connected to internet
Claude Pro or Team subscription (Cowork feature availability)

Step-by-Step

Step 1: Open Claude Desktop
        - Launch the application
        - Make sure you're logged in

Step 2: Access Cowork
        - Find the Cowork section
        - Click to open Cowork features

Step 3: Enable Dispatch
        - Click the "Dispatch" button
        - A QR code appears on screen

Step 4: Scan with Phone
        - Open Claude mobile app
        - Use the in-app QR scanner
        - Point camera at desktop QR code

Step 5: Confirm Connection
        - Wait for confirmation on both devices
        - Connection persists across sessions

Total Time: ~2 minutes

That’s it. No API keys. No configuration files. No server setup. Just scan and go.

What Actually Works

After testing various tasks, I found a clear pattern in what works reliably versus what’s inconsistent.

Works Well (High Reliability)

Task Type	Example	Success Rate
File retrieval	”Find the Q4 budget and show total marketing spend”	High
Email summary	”Summarize unread emails from this morning”	High
Document search	”Search Documents for files mentioning API redesign”	High
Meeting prep	”Pull up the project timeline and summarize milestones”	High
Simple queries	”What’s in my notes about the client meeting?”	High

These tasks have a straightforward execution path. Claude finds the information and returns it. No complex tool chaining.

Inconsistent (Research Preview Quality)

Task Type	Example	Success Rate
Multi-step workflows	”Find the report, summarize it, draft an email, send to team”	~50%
Chained connectors	”Search Slack for thread, pull attachments, upload to Drive”	~50%
Tasks ending with send/share	”Draft response and send to client”	Inconsistent

MacStories documented this ~50% success rate on complex workflows. The issue isn’t the task planning - it’s the reliability of chaining multiple tools together.

Common Mistakes I Made

Mistake 1: Expecting Desktop to Work While Asleep

I assumed Dispatch would wake my computer. It doesn’t.

Claude Desktop MUST be running and awake for Dispatch to work.

If your computer is:
- Sleeping     -> Tasks won't execute
- Powered off  -> Tasks won't execute
- Claude closed -> Tasks won't execute

I now keep Claude Desktop running when I expect to use Dispatch remotely.

Mistake 2: Trusting Complex Workflows

I tried to automate my entire morning routine from my phone:

"Check my calendar, find relevant documents for each meeting,
draft preparation notes, and email me a summary."

This failed about half the time. Each step introduces potential failure points.

Solution: Break complex tasks into simpler ones:

Task 1: "Check my calendar and list today's meetings"
Task 2: "Find documents related to the client presentation"
Task 3: "Draft preparation notes for the client meeting"

Simpler tasks have higher success rates.

Mistake 3: Ignoring Network Requirements

I tried using Dispatch on a train with spotty connectivity. The mobile app seemed to accept my task, but nothing happened on my desktop.

Both devices need stable internet. The communication flows through Claude’s servers, not directly between devices.

Why Dispatch Is Useful

Despite the reliability limitations on complex tasks, Dispatch solves a real problem:

1. Context Access Without Cloud Sync

I have files I don’t want in cloud storage. Sensitive project documents, local databases, development environments. Dispatch lets Claude work with these files without moving them anywhere.

2. True Remote Execution

This isn’t just accessing cloud-stored conversations. The task actually runs on my desktop, with access to my local file system, installed tools, and applications.

3. Persistent Conversation Sync

The conversation syncs between devices. I can start on my phone during commute, continue on desktop when I arrive, and the context carries over.

When to Use Dispatch vs Alternatives

Use Dispatch when:
- You need access to local files
- Task is relatively simple (file lookup, search, summary)
- Your desktop is running and awake

Use Cloud Chat when:
- You don't need local file access
- Task is purely informational
- You want guaranteed reliability

Use Remote Desktop when:
- You need to see and interact with your screen
- Task requires GUI interaction
- You're doing complex file operations

The Research Preview Caveat

Claude Dispatch is labeled as a research preview feature. This explains the inconsistent reliability on complex workflows.

Based on community testing and MacStories’ evaluation:

Simple tasks (file lookups, searches, summaries): Works reliably
Complex workflows (multi-step, chained tools): ~50% success rate
Tasks involving send/share actions: Least reliable

Anthropic is actively developing this feature. Expect improvements as it matures beyond research preview.

Real-World Example

Here’s a typical successful Dispatch session:

On my phone (commuting):

Me: "Find the API documentation in my project folder and summarize
the authentication endpoints."

Claude: [After a few seconds]
I found the API documentation in /projects/myapp/docs/api.md.
Here are the authentication endpoints:

1. POST /auth/login - Accepts email/password, returns JWT token
2. POST /auth/refresh - Refreshes expired tokens
3. POST /auth/logout - Invalidates current session

All endpoints require HTTPS and include rate limiting (100 req/min).

On my desktop (arrived at office):

The same conversation appears in Claude Desktop. The task executed while I was away, and I can continue working with that context.

Summary

Claude Dispatch offers a genuinely useful way to extend your AI assistant beyond your desk. The setup is remarkably simple - just scan a QR code with no technical configuration required.

Key takeaways:

Setup takes 2 minutes, no API keys or config files
Simple tasks (file lookups, searches, summaries) work reliably
Complex workflows have ~50% success rate - this is research preview
Your desktop must be running and awake
Both devices need internet connectivity

For the right use cases - quick file queries, document searches, preparing work while away from desk - Dispatch is a powerful addition to the Claude ecosystem. As the feature matures from research preview, expect improved reliability on multi-step workflows.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

👨‍💻 Claude AI Subreddit
👨‍💻 MacStories Claude Dispatch Review

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!