Dispatch Connect to Recent Conversations

Claude Cowork Dispatch should allow me to identify recent conversations that match the intent of a prompt and connect Cowork to the conversation to continue it rather than working in Cowork's single thread of activity. The ability to explicitly attach to a recent conversation and have Cowork marshal the I/O from the remote device into it would be a game changer. I already have this capability to connect to a specific session with /remotecontrol in Claude Code. My days- or weeks-long chats within Projects should also have this ability to be connected remotely.

Oftentimes, I'll have an idea while at a concert with friends and want to execute the next step from a machine that's inside my secure network that has access to all the local MCP tools configured. Cowork Dispatch can already do that but it can't find and bind a prior conversation to the stream of work. The connection to the prior conversation should be explicit and deliberate. Cowork should give me choices and allow me to explicitly pick a prior conversation to bind it and then channel the I/O from the remote device into from the dispatching machine context. This would give Cowork all the context it needs as well as access to locally configured MCP tools inside my secure network.

Additional Context

Related prior art: #41273 ("Dispatch: attach to existing cowork sessions instead of always spawning new ones") established the underlying need for Dispatch to bind to something other than a freshly-spawned session, but was scoped only to active/live Cowork sessions and was closed as not_planned. This request extends that idea to any recent conversation — including days- or weeks-old Projects chats that aren't currently running a session — via an explicit picker, with the dispatching machine's local MCP tool access carried into the bound conversation.