How to Build a Safe Claude Dispatch Workflow on Your Phone

Claude Dispatch lets you assign and follow Cowork tasks from a persistent thread that you can access on Claude Desktop or the Claude mobile app. It is useful when you are away from your desk but your computer and approved work resources are available to Claude.

A good mobile workflow is narrow, reversible, and easy to verify. Start with reading, organizing, summarizing, or drafting. Avoid making the first version responsible for sending messages, deleting files, publishing changes, moving money, or handling sensitive records.

Understand which Claude feature you are using

Dispatch in Cowork and Claude Code Remote Control both provide mobile continuity, but they are not interchangeable:

• Cowork Dispatch uses a persistent Cowork thread for assigning tasks from Claude Desktop or mobile. The thread retains earlier task context.
• Claude Code Remote Control connects a phone or browser to a Claude Code session running on your computer. The local environment, filesystem, tools, and project configuration remain available to that session.
• Claude Code on the web runs on cloud infrastructure rather than being merely a window into a local Remote Control session.

Use the instructions for the exact surface shown in your account. Plan and workspace availability can change, and organizational admins may need to enable some capabilities.

1. Choose a real off-desk scenario

List moments when you are away from the computer but could safely review work on your phone—for example, riding public transit, waiting before a meeting, or sitting in an airport lounge. Do not operate a workflow while driving or whenever the phone would distract you from your surroundings.

For each situation, record:

• the typical amount of uninterrupted time;
• which tasks accumulate during that period;
• which information the task must read;
• whether it needs to write or change anything;
• how you can verify the result from the phone;
• what should happen if the task cannot finish safely.

Choose one frequent task with a clear output. “Read three project notes and draft a status summary” is a stronger first workflow than “handle everything that arrived today.”

2. Prepare the desktop environment and permissions

Before leaving your desk:

• Update Claude Desktop and the Claude mobile app.
• Confirm that Dispatch is available for your plan and workspace.
• Open the intended Cowork thread and verify that the phone shows the same thread.
• Connect only the files, folders, apps, browser sites, and connectors required for this workflow.
• Remove unrelated sensitive documents from the visible workspace.
• Keep the computer powered, online, and awake for any task that depends on it.
• Run a harmless test, such as listing filenames in an approved folder without changing them.
• Enable notifications only if they will help you respond to permission requests or completion notices.

Do not assume that working through your own computer means no information is transmitted. Review Anthropic's current privacy, retention, workspace, and connector terms for your account before using confidential material.

3. Write the workflow before running it

Use this template:

Workflow name:
When I use it:
Allowed sources:
Allowed outputs:
Actions that require confirmation:
Actions that are prohibited:

Pre-departure check:
- Desktop and mobile apps updated
- Correct Cowork thread open
- Required computer, files, and apps available
- Minimum necessary permissions granted
- Sensitive unrelated material closed
- Recovery path tested

Step 1 — Read:
Prompt:
Expected result:
How I verify it:
If it fails:

Step 2 — Analyze or draft:
Prompt:
Expected result:
How I verify it:
If it fails:

Step 3 — Save:
Prompt:
Exact output location:
How I confirm the file exists and is correct:
If it fails:

Final human action:
What I will review or send manually:

Keep one objective per prompt. Separate reading from writing so you can inspect the evidence before allowing a file change.

4. Example: prepare a project update while commuting

This example is for a passenger on public transport, not a driver.

1. Read: “Read the Markdown files modified this week in [approved project-notes folder]. List each filename and its last modified date. Do not change any files.”
2. Summarize: “Using only those files, draft a project update with Completed, Blocked, and Next sections. Put uncertain items under Questions. Cite the source filename after each bullet.”
3. Save: “Save the draft as [approved drafts folder]/project-update-draft.md. Do not overwrite an existing file; if the name exists, stop and tell me.”
4. Verify: “Read the saved file back, confirm its path, and compare each bullet with its cited source. Report any unsupported statement.”
5. Human finish: review the draft at a desk, correct it, and send it through the normal communication channel.

This workflow creates a draft without sending it, preserves traceability to source files, and has an explicit no-overwrite rule.

5. Test every step twice

Run the full sequence with non-sensitive sample files. Record what happened instead of judging success from a confident completion message.

Step	First attempt	Verified result	Prompt adjustment	Second attempt
1
2
3
4

For a write step, verification means reopening the exact file, checking its content, and confirming that no unintended file changed. For a browser or app action, it means checking the resulting state directly.

6. Measure whether the workflow saves time

Do not use task count as a proxy for value. Measure several real runs:

Net time saved = normal desk time ? total Dispatch handling time

Total handling time includes writing prompts, waiting when attention is required, approving permissions, checking output, correcting errors, recovering from failures, and completing the final manual action. Also record whether the workflow introduced a quality or security risk that makes the time saving irrelevant.

Measure	Record
Baseline	Time required to complete the task normally at a desk
Mobile effort	Active time spent prompting, monitoring, and responding
Verification	Time spent checking sources, files, and final state
Rework	Time spent correcting or repeating failed steps
Outcome quality	Complete, partially usable, or unusable
Risk events	Unexpected permission request, wrong file, unsupported claim, or unintended action

Keep the workflow only if repeated tests show a useful, safe improvement.

7. Set limits for browser and computer use

In Cowork, Claude may use a connector, a browser, or direct screen interaction. Direct computer use can see screenshots and interact with desktop apps, and Anthropic states that there is no sandbox between Claude and those applications. Grant per-app access carefully.

• Avoid financial accounts, investments, legal documents, medical information, and apps containing other people's sensitive personal data.
• Do not allow a page, email, or document to expand the task or override your instructions. Untrusted content can contain prompt injection.
• Require confirmation before sending, publishing, purchasing, deleting, overwriting, or changing access permissions.
• Prefer supported connectors over screen automation when both are available, then verify the result in the destination system.
• Use a narrowly scoped working folder and version control or backups for recoverability.
• Stop if the task requests unexpected credentials, permissions, downloads, or navigation to an unfamiliar domain.

Good and poor candidates for Dispatch

Good first workflows	Workflows to avoid or keep human-controlled
Read-only summaries with source filenames	Banking, investing, payments, or purchases
Drafts saved to a dedicated folder	Medical, legal, or sensitive personnel records
Sorting or renaming copies of non-sensitive files	Permanent deletion or broad file moves
Code or document review notes that a person will post	Production deployment without independent checks
Meeting preparation from approved notes	Sending external messages without final review

Keep a reusable record

Save the tested workflow where you can reach it from the phone. Include exact prompts, allowed locations, expected output, verification steps, and the fallback. Review it after app updates or permission changes because product behavior may change.

Anthropic's official guide to assigning Cowork tasks from anywhere explains the persistent thread. Its computer-use guidance describes permissions and sensitive-data risks. Developers who need a local coding session should use the separate Claude Code Remote Control documentation.

For adjacent setup and evaluation guidance, see how to install Claude Code on Windows 11 and this comparison of ChatGPT, Claude, and Gemini.