[BUG] Dispatch unreachable in Claude Desktop on macOS (2.31226.1, Max plan): Settings search finds it but no toggle renders, visible on mobile

Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 10, 2026

Preflight Checklist

  • [x] I have searched existing issues. The closest are #80058 (macOS, closed as duplicate), #77071 (Windows, open) and #87253 (Windows). None covers this exact symptom on the current macOS build.
  • [x] This is a single bug report
  • [x] I am using the latest version of the Claude desktop app (auto-updater reports nothing newer)

What's Wrong?

Dispatch is available in the Claude mobile app, but it cannot be enabled or reached anywhere in Claude Desktop on macOS, on the same account.

  • The desktop sidebar shows only Chat and Code. There is no Cowork entry and no Dispatch entry.
  • Searching "Dispatch" in Settings returns a result that points at Settings > This computer > System. Clicking the result opens the System page, but no Dispatch section or "Enable Dispatch" toggle is rendered there. The page shows the System block (app version, shortcuts, menu bar, keep awake, storage) and then Browser use, with no Dispatch control.
  • Because of this there is no way to turn Dispatch on for this computer, so the phone has no desktop host to dispatch to.

Environment

  • Claude Desktop: 2.31226.1 (macOS, arm64)
  • macOS: 27.0 (26A428)
  • Hardware: Apple M4 Pro
  • Plan: Max ($100), personal account (not Team or Enterprise)
  • Same account signed in on desktop and mobile
  • Mobile app: Dispatch is visible

What Should Happen?

The System settings page should render the Dispatch section with the "Enable Dispatch" toggle (the app ships the strings "Enable Dispatch" and "Let Claude work on tasks from your phone using this computer"), or Dispatch should appear in the sidebar. If Dispatch is intentionally gated off for this account or build, the Settings search should not return it, and the app should say why it is unavailable.

Steps to Reproduce

  1. Sign in to Claude Desktop 2.31226.1 on macOS 27.0 with a Max plan personal account.
  2. Note that the sidebar has Chat and Code only.
  3. Open Settings and type "Dispatch" in the search box.
  4. Click the result. It navigates to This computer > System.
  5. Scroll the whole page. No Dispatch section or toggle is present.
  6. Open the Claude mobile app on the same account. Dispatch is present there.

Already Tried

  • Fully quit (Cmd+Q) and relaunched, several times
  • Confirmed the same account email on both devices
  • Confirmed the app is current: updater last seen version and running version are both 2.31226.1, nothing staged
  • "Keep computer awake" is on

Diagnostics from local logs

  • vm-support-probe.json reports "virtSupport":"supported" for 2.31226.1|27.0.0|arm64. The app bundle has the com.apple.security.virtualization entitlement.
  • cowork_vm_node.log on every launch: the VM module loads, then [Bundle:status] rootfs.img missing, vmlinuz missing, initrd missing, initrd-micro missing. vm_bundles/warm is empty. The Cowork VM bundle has never been downloaded.
  • main.log on every launch: [WarmLifecycle:cowork] Initialized (arm=always) followed about one second later by [WarmLifecycle:cowork] Destroyed, right after account details arrive. LocalAgentModeSessionManager then reports Initialization succeeded with 2 existing sessions.
  • [remote-tools-device] connects to the bridge, logs authenticated and device registered, so the device bridge itself works.
  • ~/Library/Application Support/Claude/bridge-state.json does not exist.
  • No Dispatch related log lines are ever written on desktop.
  • claude.ai-web.log shows [REACT_QUERY_CLIENT] QueryClient error: {"name":"Error","message":"Not found"} around the time the Settings page was opened. The log does not include the request path, so I cannot confirm it is the Dispatch query.

Notes

This looks like a server side entitlement or flag mismatch between mobile and desktop for the same account, or a Settings section that is indexed for search but gated off at render time. Reinstalling was not attempted because other reporters (#87253) found it did not help.

View original on GitHub ↗