[BUG] Control panel navigation lacks visual affordance for switching between Claude experiences (Cowork / Chat)
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Type: UX / Design feedback
Description:
In the redesigned Claude control panel, the navigation options for switching between different Claude experiences (Cowork, Chat, and the control panel itself) are not visually distinguishable as interactive buttons. As a user, it was non-obvious that these three options were clickable and would navigate me to a different Claude surface.
Current behavior:
The three navigation options render without clear visual boundaries, making them appear as static labels or headings rather than interactive controls.
What Should Happen?
Expected behavior:
The three options should have clear visual affordance indicating interactivity — for example:
A border/outline around each option to group them as a button cluster
Button-style backgrounds or hover states
Clearer visual separation between "current location" and "navigate to"
Impact:
Users may not discover that they can easily switch between Cowork and Chat from the control panel, reducing cross-surface navigation and making the experiences feel more siloed than intended.
Suggested fix:
Add a container/border around the three navigation options and apply consistent button styling so they read as a clickable navigation group.
Error Messages/Logs
Steps to Reproduce
navigate to claude app
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.81 (Claude Code) but also it says i'm on 1.3109.0 (but i'm not able to copy that text either--that should be another bug!)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗