[BUG] Code sessions started via Dispatch don't appear in mobile Dispatch list

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Summary
When a Dispatch (Cowork) session on desktop spawns a Code task (a session that runs against a real git repo on the host machine, shown in the desktop "Code" tab), that session does not appear in the Dispatch list on mobile/tablet devices — even though regular Cowork (non-code) tasks spawned in the same conversation DO appear correctly.

Environment

• Desktop: Windows, Claude desktop app (Cowork mode)
• Mobile: Tablet (Claude mobile app)
• GitHub connector: shown as "Connected" in Settings > Connectors, but no GitHub MCP tools were exposed to the Dispatch orchestrator session when tested

Steps to reproduce

1. On desktop, start a Dispatch conversation.
2. Ask Claude to start a regular Cowork task (e.g. "write a note in Notepad") — this spawns via start_task.
3. Ask Claude to start a task that requires editing a real git repository (e.g. "open my project in C:\\path\\to\\repo and make a change on a new branch") — this spawns via start_code_task and shows up in the desktop's "Code" tab.
4. Open the Claude mobile/tablet app and go to the Dispatch list.

Expected behavior
Both sessions (the regular Cowork task and the Code task) should appear in the Dispatch list on mobile, ideally the Code session with a distinguishing "Code"/"Dispatch" badge, plus a push notification when it finishes or needs approval.

Actual behavior
Only the regular Cowork task(s) appear in the Dispatch list on mobile (confirmed via screenshot: two Cowork tasks were visible). The Code task started in the same conversation, around the same time, does not appear anywhere in the mobile Dispatch list, despite:

• Both the desktop app and mobile app being up to date
• Dispatch QR pairing already completed and working (confirmed by the Cowork tasks syncing correctly)
• The desktop app remaining open/awake the entire time

Additional notes
This makes it impossible to check progress, respond to blocking questions, or get completion notifications for Code sessions while away from the desktop, which defeats a core purpose of Dispatch for engineering-adjacent work. Not clear whether this is a sync bug specific to Code-tab sessions, or an intentional scoping limitation that isn't documented/surfaced to the user.

What Should Happen?

Code sessions (started via start_code_task, shown in the desktop "Code" tab) should appear in the mobile Dispatch list alongside regular Cowork tasks, with a "Code"/"Dispatch" badge, and should trigger a push notification when they finish or need approval — matching the behavior of regular Cowork tasks, which already sync correctly to mobile.

Error Messages/Logs

Steps to Reproduce

1. On desktop, start a Dispatch (Cowork) conversation.
2. Ask Claude to start a regular Cowork task (e.g. "write a note in Notepad") -- this spawns via start_task.
3. Ask Claude to start a task that requires editing a real git repository (e.g. "open my project in C:\path\to\repo and make a change on a new branch") -- this spawns via start_code_task and shows up in the desktop's "Code" tab.
4. Open the Claude mobile/tablet app and go to the Dispatch list.

Result: Only the regular Cowork task from step 2 appears in the list. The Code task from step 3, started in the same conversation around the same time, is missing entirely from the mobile Dispatch list.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

N/A -- reported from Claude desktop app (Cowork/Dispatch), latest available version as of 2026-07-17. Not using the raw CLI for this report.

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

Related issues I checked but which don't seem to cover this exact case:

• #72586 (closed as duplicate) — about sessions that existed BEFORE pairing becoming invisible after pairing.
• #57754 (closed as duplicate) — a feature request for Dispatch to surface pre-existing local sessions; the reporter there says self-spawned-from-Dispatch sessions already work fine for them.
• #77071 (open) — about the Dispatch tab/entry being completely missing from the sidebar, which is a different symptom (Dispatch works fine here, just this one session type doesn't sync).

Our case: the Code session was spawned BY Dispatch itself, in the same conversation, and still never appeared on mobile — while a plain (non-code) Dispatch task spawned moments earlier in the same conversation did sync correctly. Happy to provide the desktop app version number or additional screenshots if helpful.