Four UX/Product Gaps Identified in Claude's Onboarding Experience

Dispatch Issues

1. No graceful timeout when desktop is offline: If you send a Dispatch task while your Mac is off or the Claude Desktop app is closed, the task enters an infinite run loop with no timeout, no failure notification, and no auto-stop. This silently drains both battery and usage allocation with no way to know it's happening unless you manually check. Expected behavior: task should fail gracefully, notify the user, and stop consuming resources.

2. Single persistent thread with no ability to create separate threads: All tasks sent through Dispatch — regardless of project, topic, or workflow — get appended to one permanent background conversation. There is no way to create separate Dispatch threads for different workstreams (e.g. one for prospecting, one for research, one for scheduled tasks). For users managing multiple ongoing workflows this creates a cluttered, hard-to-navigate log.

Claude in Chrome Issue

3. Chat panel is tab-anchored, not group-level: Within a Claude tab group, the chat panel attaches to a specific tab rather than floating across the group. If you open LinkedIn in one tab and Outlook in another, the chat is only accessible from whichever tab it was originally opened in. Clicking 'open chat' from another tab redirects you back to the original tab rather than surfacing the chat in context. For multi-tab workflows this creates constant context switching — the opposite of what the tab group feature is designed to solve.

Mobile App Issue

4. Google Drive connector files not visible in project knowledge base UI: In a Chat Project with both manually uploaded files and Google Drive connector files, the mobile app only displays manually uploaded files in the knowledge base panel. Drive-connected files are invisible in the UI, creating a misleading impression that the project's knowledge base is incomplete. The files are still accessible to Claude during conversation, but the discrepancy between what's shown and what's actually available is confusing — especially for users who rely on Drive-heavy workflows.

All four issues were reproduced consistently during a single onboarding session on Claude Pro / macOS.