[Bug] Dispatch routes to Claude Desktop Code tab instead of Claude Code CLI in Warp terminal

Bug Description

Dispatch → Warp Routing Regression — Feedback for Anthropic

_Date: 2026-05-20 | Surface: Phlaude Dispatch_

@tkunst

---

Summary

Code tasks dispatched from Phlaude Dispatch no longer route to the Claude Code CLI session running in Warp terminal. They now route to Claude Desktop's Code tab (sandboxed VM) instead. This breaks the core Dispatch use case for Mac-native operations.

---

Expected Behavior (previously working)

When both of the following were true:

• Claude Desktop was open
• Claude Code CLI (claude) was actively running in Warp terminal

...Code tasks started from Phlaude Dispatch would appear as sessions inside the Warp terminal. The user could see them in Warp and the tasks ran with full Mac-native access (filesystem, iCloud Calendar via osascript, iMessage via chat.db, git on external drives, etc.).

---

Current Behavior (broken)

Same conditions — Desktop open, claude running in Warp — but Code tasks now route to Claude Desktop's Code tab and run inside the sandboxed Linux VM. The VM cannot:

• Read ~/Library/Messages/chat.db (Full Disk Access doesn't apply)
• Run osascript (no AppleScript host)
• Write to git repos on external drives (sandbox permission)
• Access iCloud calendars

The "Allow Claude to use Bash?" permission prompt appears on the phone (Phlaude), confirming the sandboxed VM is running the task, not the Mac-native Warp session.

---

What Was Tested

1. Both Desktop + Warp CLI open → routes to Desktop Code tab (sandboxed VM) ❌
2. Desktop closed, Warp CLI open → "Can't reach your desktop. Check that your computer is online and desktop app is open." ❌
3. Manually running same task in Warp CLI → works, has FDA, reads chat.db ✅

---

Impact

Dispatch's value proposition is running Mac-native Code tasks from a phone without sitting at the Mac. Routing to the sandboxed VM instead of the Warp CLI session removes the primary use case. The user had a working setup that broke without any changes on their end — this appears to be a regression introduced in a Claude Desktop update.

---

Environment

• Machine: Mac Mini M4, macOS 26.3.1
• Claude Desktop: current version (Daude)
• Phlaude: current version (iOS)
• Warp terminal with claude CLI running 24/7
• Full Disk Access granted to /opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/bin/claude

---

Requested Fix

When a claude CLI session is actively running in a Mac terminal (Warp / Terminal.app), Code tasks dispatched from Phlaude should route to that session — not to Desktop's sandboxed Code tab. This was the behavior previously and it was the correct behavior for Mac-native task execution.

Environment Info

• Platform: darwin
• Terminal: WarpTerminal
• Version: 2.1.145
• Feedback ID: c7717fe5-1b1c-4abc-9708-767011115358

Errors

[]