Claude Dispatch Guide: Setup, Requirements, Use Cases, and Safety

Claude Dispatch lets you initiate or continue tasks from your mobile device while Claude performs the work using your configured desktop environment. You send a request from your phone, Claude accesses your files, apps, email, Slack, and other tools already set up in Cowork, and returns results or asks for approval when needed.

Unlike regular Claude chat, Dispatch uses a persistent conversation thread, so context carries across sessions. You can assign a task, move on, and come back later—Claude remembers your project context and previous instructions.

Persistent thread: Each Dispatch conversation maintains a continuous thread. This means Claude retains context across multiple tasks and sessions, avoiding the reset that happens in standard chat.

Context carries forward: Your work history, preferences, and project details persist. If you ask Claude to process files a certain way, it remembers that preference for future tasks.

Claude returns outcomes: After completing a task, Claude sends results back to your mobile device. This might be a summary, a processed file, a briefing, or a confirmation that the work is done.

Push notifications: Claude can notify you when a task completes, or when it needs your approval before proceeding with a sensitive action.

One thread only: Dispatch uses a single persistent conversation for everything. There is currently no way to create separate threads for different projects, start fresh, or run parallel Dispatch conversations. All your messages and task history live in one continuous thread.

Dispatch lives in the Cowork tab, but it doesn't always run work there. When you send a task from your phone, Claude decides which environment to use:

When a task routes to Claude Code, a new session appears in the Code tab sidebar with a Dispatch badge. You still get a push notification on your phone when it finishes or needs your approval.

You don't need to choose — Claude picks the right environment based on what you ask for. If you want to force a Code session explicitly, say so directly: "Open a Claude Code session and fix the login bug."

File access: Claude has access to files and folders you've configured in Cowork. This includes local file systems, cloud storage integrations, and any other connected data sources.

Outputs: Files that Claude creates or modifies are saved to your desktop or cloud storage. You can retrieve results from either your mobile app or by checking your desktop file system.

Memory: The persistent thread retains context, instructions, and user preferences. Memory carries work forward and helps Claude understand your style and priorities across multiple tasks.

Memory control: You can view, edit, and delete memory entries at any time. If Claude is remembering something incorrectly, you can correct it or clear it entirely.

⚠️ Claude Dispatch can trigger real actions on your computer. Please read this section carefully.

Real consequences: Mistakes or malicious instructions can have real impact. If you tell Claude to delete files, it will delete them. If Claude misunderstands an instruction, data could be lost or altered.

Understand your access: Know which files, apps, and integrations Claude can access through your Cowork setup. Limit access to only what Claude needs.

Know how to revoke access: You can disconnect integrations, remove file permissions, or disable Dispatch entirely at any time from Cowork settings.

Desktop must stay active: Your computer must remain awake and connected to complete tasks. Put your computer to sleep, disconnect from the network, or close the Claude app, and tasks will pause.

Computer use scope: When using computer-use features, Claude may operate outside the Cowork sandbox and interact directly with your desktop environment. Be explicit about what you want automated.

Single conversation thread: All Dispatch activity lives in one thread. You cannot separate work by project or client. If context from one task bleeds into another, be explicit about project context in your instructions, or correct Claude's memory entries.

Review before approval: If Claude asks for approval before taking a sensitive action, review the details carefully before allowing it to proceed.