[FEATURE] Let a Claude Code session deliver files and messages back into Dispatch

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Problem Statement

Dispatch only goes one way. From my phone I can hand a task to Dispatch and it runs on my desktop — but when the session produces something I want to read on my phone, there is no way to send it back. The running session has no tool that targets Dispatch, and Dispatch never appears as a destination in the session's toolset.

Concretely, today: I asked Claude Code to compile a contact list from files on my PC, and asked for the result somewhere I could read it on my phone. The session couldn't deliver into Dispatch, so we ended up doing all three of these instead:

• copying the file into the Google Drive folder synced on the machine;
• publishing a claude.ai artifact — which turned out not to appear in the Claude mobile app's gallery, only in a mobile browser at claude.ai/code/artifacts;
• creating a Google Doc through the Drive connector.

All three work. All three route around the product. Dispatch was the surface I was already using and the first place I looked.

Proposed Solution

Proposed Solution

Give a running session a way to post back into the Dispatch conversation on the same account — a message, and ideally an attached file.

Something like a SendToDispatch({ message, files }) tool that appends a turn to the Dispatch conversation, so the result shows up in the Cowork tab on the phone. An attached file should surface the way a file shared into a chat does.

Even a text-only version would be a real improvement. The important part is that the phone side hears back without the user having to remember a link or open a browser.

Alternative Solutions

Alternative Solutions

• Google Drive (sync folder, or the Drive connector to create a Doc). Works, but requires Drive and drops work files into a personal Drive.
• Publishing a claude.ai artifact. The URL opens fine in a mobile browser, but Claude Code artifacts don't appear in the mobile app's gallery — so on the phone it's a link you had to keep somewhere.
• Emailing myself. An extra step, and the Gmail connector here can only create a draft, not send.
• Running the whole thing as a cloud session on claude.ai/code. Changes where the work runs purely to change where the result is read.

Priority

Medium — workarounds exist, but every one of them has to be set up before you walk away from the desk.

Feature Category

Closest match to the desktop app / Dispatch integration.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

Use Case Example

1. From my phone, I ask Dispatch to compile a list from files on my PC.
2. Dispatch spawns a Claude Code session on the desktop; it reads the files and produces the list.
3. I'm out of the house. I open the Claude app expecting to see the result.
4. Today: nothing. The session finished, the file sits on the PC, and I see it when I'm back at my desk — unless I arranged a workaround in advance.
5. With this feature: the session posts the list back into Dispatch, and it's on my phone.

Additional Context

Additional Context

The asymmetry is the whole point. Dispatch is documented as the way to hand work to your computer from your phone, but the return trip only exists if the user builds it themselves. Anything that ends up as a file — a report, a list, a diff summary, a screenshot — currently has no path home.