claude-code - 💡(How to fix) Fix [Feature Request] Cross-tool orchestration: unified routines, memory, and session management across Claude Code, Dispatch, and web UI [1 comments, 2 participants]

Feedback: Claude’s tools need to talk to each other

The problem

Claude Code, Dispatch (Cowork), and Routines are three separate systems that can’t see each other’s state or trigger each other’s work. As a user, I experience them as one product, but they behave like three products that happen to share a login.

Specific gaps I’ve hit:

• Routines aren’t accessible from Dispatch. I set up a routine at claude.ai/code/routines. Dispatch (my primary interface, since I’m often on mobile) can’t see it, can’t trigger it, and can’t read its output. If I want Dispatch to run the same job on demand, I have to recreate it as a
• Dispatch scheduled task and maintain it in two places.
• Dispatch can’t reliably delegate to Claude Code sessions. Dispatch starts code tasks on the desktop, but they frequently hang, and Dispatch has no way to kill or restart them. From mobile, I can’t see what’s happening in those sessions at all. When a task gets stuck, the only option is to wait or ask the orchestrator to start a new one.
• Memory doesn’t persist across restarts. Dispatch’s auto-memory folder was empty after an app restart, losing all context from prior conversations. This meant re-deriving preferences, project state, and working context from scratch. The orchestrator also couldn’t fall back to Claude Code’s memory (different system).
• Code sessions can’t access Dispatch context and vice versa. A code session I started from Dispatch didn’t know about files on my Desktop. Dispatch didn’t know that a prior Claude Code session had already completed half the work in my manifest. Each system starts from zero.

What I expected

One orchestrator that can: • See and trigger routines I’ve already set up (regardless of where I created them) • Monitor and manage code sessions it spawns (kill, restart, read output) without requiring me to be at the desktop • Share a single persistent memory layer across all Claude surfaces • Access the same file context, whether I started the conversation from mobile, desktop, or a routine

Why it matters

I’m trying to use Dispatch as a high-level orchestrator across multiple projects. That’s the right shape for it. But the value breaks down when it can’t coordinate with the other Claude tools I’m already using. I end up spending time bridging the gaps manually (re-explaining context, recreating routines, copying output between systems) instead of doing actual work.

Suggestions 1. Shared routine/task registry. Routines created anywhere should be visible and triggerable from anywhere: Dispatch, Claude Code, the web UI. 2. Shared persistent memory. One memory layer that all Claude surfaces read from and write to. If I tell Claude Code something, Dispatch should know it next session. 3. Better code session management from mobile. At minimum: see running sessions, read their output, kill stuck ones. Dispatch spawns these sessions but currently has no visibility into them from the iOS app. 4. Unified file context. If Dispatch needs a file, it should be able to find it without me specifying the exact path. At least let it search common locations or remember where things were last session.