Direct answer
Claude Dispatch is a long-running agent in Cowork. It accepts one high-level outcome, splits it into child tasks, and runs background Cowork or Code sessions. You can start from Claude Desktop or the mobile app, then review each transcript and result. Use it for bounded work you can inspect later. Keep the desktop host awake for tasks that depend on its files, tools, or apps.
Summary
- Dispatch provides one conversation that plans and delegates several child tasks.
- Coding work routes to a configured Code workspace. Knowledge work routes to a Cowork project.
- Each child task has a status, transcript, produced files, permission prompts, and a final result.
- Mobile access uses the same Dispatch conversation while Claude Desktop remains available as the host.
- The feature expands access to local files, connectors, plugins, and potentially desktop apps. Use narrow access and human review.
- Choose Remote Control when you want to continue one live Claude Code conversation instead of delegating new background work.
What Claude Dispatch does
Dispatch appears as one conversation in the Claude sidebar. You describe an outcome rather than managing every step. The agent creates one or more child tasks, assigns each to the suitable surface, and shows their status beneath the Dispatch group. A child task cannot create another generation of children.
Coding work runs through Code against a workspace you have already configured. Knowledge work runs through Cowork in the project you name or the available default. You can name the workspace or project in the brief. Otherwise, Dispatch can list what is available and choose.
Check Anthropic's current Dispatch workflow, routes, states, permissions, and mobile instructions.
Check the current requirements
- Plan
- the current Dispatch documentation lists Pro and Max. Availability may change during beta or research preview.
- Desktop
- install the latest Claude Desktop app, sign in, and complete Dispatch setup.
- Mobile
- install the current Claude app and use the same account when you want to assign work away from the computer.
- Host
- leave the desktop app open and the computer awake and online for work that depends on the host.
- Context
- prepare the required Cowork project, Code workspace, folders, connectors, plugins, and app access before leaving.
- Platform
- current help lists macOS, Windows x64, and a Linux beta. Linux currently lacks computer use but can use files, connectors, and plugins.
Avoid reducing the architecture to `everything runs locally`. Anthropic's Cowork safety guide describes isolated remote session execution that can reach permitted local resources through Claude Desktop. Dispatch documentation also describes a desktop host and Code workspaces. The important question is which files, services, apps, network locations, and execution surfaces each child task can reach.
Set up Dispatch
- Update Claude Desktop and the mobile app, then sign in with the same eligible account.
- Open Cowork and select Dispatch in the left sidebar.
- Review the setup explanation and choose whether to allow file access or keep the computer awake.
- Create or review the Cowork projects and Code workspaces that Dispatch may use.
- Grant only the folders, connectors, plugins, and applications required for the first test.
- Start with a reversible read-only task and confirm that the mobile and desktop conversation stays synchronized.
- Inspect the child transcript, output, and any permission event before expanding access.
Use the current mobile-to-desktop setup and limitation guide from Anthropic's Help Center.
Brief one outcome with clear boundaries
A strong Dispatch request names the deliverable, source, workspace or project, deadline, constraints, approval points, verification, and stopping condition. Avoid `clean up my work`. Prefer a bounded request that identifies the folder, allowed changes, required report, excluded actions, and final checks.
Outcome: produce [deliverable] for [audience]. Work in [Cowork project or Code workspace]. Use only [sources, folders, and tools]. Forbidden actions: [send, publish, buy, delete, merge, or contact anyone]. Ask before [specific action]. Save the result to [location]. Verify it with [checks]. Stop and report if [risk or missing input] appears.
Read child-task status correctly
- Running
- Claude is actively working.
- Awaiting input
- the task needs information before it can continue.
- Awaiting answer
- a question is waiting for your reply.
- Completed
- the child stopped with a reported result. Completion does not prove correctness.
- Error
- the task stopped because something failed. Read the transcript before retrying.
- Archived
- you marked the task as finished and moved it aside.
Select any child to read its full transcript, review the steps, inspect files, and send a follow-up. A polished summary can omit a failed attempt, assumption, or blocked permission. The transcript and actual artifact provide stronger evidence than the completion label alone.
Respond to permissions in time
When a child needs permission, Dispatch forwards the request. Current documentation says an unanswered request is automatically denied after ten minutes, then the task continues without that action. A denial may create a partial result rather than a visible failure. Review what was skipped before accepting the output.
- Confirm the child, project, file, app, account, command, and intended change before approval.
- Approve the smallest useful scope and duration.
- Deny a request whose target or effect is unclear, then give a safer path.
- A notification alone is not enough to approve money movement, publication, destructive changes, production actions, or external messages.
- Review the resulting diff, document, message draft, transaction state, or app history after the action.
Protect the desktop chain
Mobile Dispatch can reach resources connected to the desktop host. That chain may include local files, connectors, plugins, browser sessions, developer tools, and desktop applications through computer use. A malicious document, message, page, or prompt can influence the task. Limit both what Claude can read and what it can change.
- Account
- protect the Claude account and every connected device with current authentication and device controls.
- Folders
- expose a dedicated working folder instead of an entire home, cloud-drive, or customer-data tree.
- Connectors
- connect only the service and account required for the task. Remove unused access.
- Plugins
- review the publisher, permissions, tools, updates, and data path before installation.
- Computer use
- prefer a direct, scoped connector or file tool when it can complete the same task with clearer boundaries.
- Recovery
- keep version control, backups, drafts, logs, cancellation, and a quick way to disconnect the host.
- Review
- keep a person close for high-impact work involving money, identity, legal duties, health, production systems, or public communication.
Read Anthropic's current Cowork risk model and safety controls before enabling broad access.
Tasks that fit Dispatch
- Research from named sources with a citation and uncertainty report.
- Drafting a memo, spreadsheet, comparison, or presentation inside a dedicated project folder.
- A code change in a configured workspace with a narrow scope, tests, and a reviewable diff.
- Organizing copied files where the originals and desired structure are preserved.
- Preparing drafts for messages, calendar events, reports, or tickets that a person will send or publish.
- Repeatable reporting when sources, schedule, output location, review, and failure behavior are explicit.
Tasks that need closer supervision
Stay present for ambiguous, irreversible, or high-stakes work. Examples include deleting originals, paying invoices, trading, changing production, sending messages, or signing agreements. The same applies to health or legal decisions, sensitive customer data, and security incidents. Dispatch can help prepare evidence and drafts, but responsibility remains with the authorized person.
Dispatch or Remote Control?
- Choose Dispatch to hand off a new outcome that can be split into background Cowork or Code tasks.
- Choose Claude Code Remote Control to continue one live local Code session from a browser or phone.
- Choose a regular Cowork session when you want to watch, redirect, and approve the work closely.
- Choose a cloud session when the task must continue without an awake desktop host and the available cloud environment fits.
Compare Dispatch with the local-session behavior in the Claude Remote Control guide.
Current limitations
- The Dispatch interface uses one continuous conversation rather than several user-created Dispatch threads.
- A child task can route to Cowork or Code but cannot spawn more child tasks.
- Desktop-dependent work stops being available when the host sleeps, closes, signs out, or loses connectivity.
- Computer use is unavailable in the current Linux beta, although other supported tools may work.
- Permission timeouts can leave a task with a partial result.
- Background completion does not remove the need to verify sources, files, tests, changes, and external effects.
Frequently asked questions about Claude Dispatch
Yes for Dispatch work that uses the desktop host. Leave Claude Desktop open and keep the computer awake and online. Use a suitable cloud session when work must continue without that machine.
Current Dispatch documentation lists Pro and Max. Beta access can change, so check the feature in your account and the current official requirement page.
It can be used more safely with narrow folders, trusted services, protected devices, reversible tasks, timely approvals, and artifact review. Risk grows with the access and actions available through the desktop chain.
Before you walk away
- The outcome, output location, source, project or workspace, and stopping condition are explicit.
- The host is awake, online, updated, and signed into the intended account.
- Only the required folders, tools, connectors, plugins, and apps are available.
- Risky actions require a person and cannot be inferred from a broad prompt.
- Notifications work and someone can respond before a permission request expires.
- The task has backups, version control, cancellation, and a recovery path.
- A named reviewer will inspect the transcript, artifacts, changes, tests, and external effects.