[FEATURE] Better multi-tasking and navigation in Claude Desktop
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
Claude Desktop's single-page navigation makes it cumbersome to switch between projects, chats, Cowork sessions, and settings. As someone who uses Desktop specifically for local integrations (Obsidian, Claude Code via MCP), I find myself constantly navigating back and forth rather than staying in flow. The friction is high enough that I've largely relegated Desktop to local-integration tasks only, using claude.ai in the browser for everything else — which largely defeats the purpose of Desktop as a primary interface.
I'm aware of several related requests (#18818, #29136, #30154, #27725) around keyboard shortcuts, split views, and multi-window support, but one gap I don't see covered is a keyboard-driven way to jump to any chat, project, or session without going through the sidebar.
Proposed Solution
A quick switcher / command palette — something like Obsidian's Cmd+P or VS Code's Cmd+K — that opens a fuzzy-searchable list of destinations: recent chats, projects, Cowork sessions, and settings. Press the shortcut, type a few characters, hit Enter, and you're there. No mouse, no sidebar scrolling.
This feels like it could be a relatively lightweight win compared to tabs or split panes (covered in the related issues above), and would address a lot of the day-to-day navigation friction on its own.
Alternative Solutions
The existing double-tap Option shortcut (quick entry) is close in spirit, but it's scoped to opening new chats and showing 5 recents — it doesn't help with navigating to a specific project, an older chat, or settings.
My current workaround is keeping claude.ai open in a browser for navigation-heavy work and only using Desktop when I need local integrations. It works, but it's a fragmented experience and means I'm not really using Desktop as a primary interface the way I'd like to.
Priority
Medium - Would be very helpful
Feature Category
Other
Use Case Example
_No response_
Additional Context
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗