[BUG] Cowork tab not showing on Windows — Intel Core i5-8265U not supported
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?
The Cowork tab does not appear in the Claude Desktop app. Only the "Chat" tab is visible in the top navigation — there is no "Cowork" option, despite having an active Pro subscription.
Environment Info
- Platform: Windows
- Processor: Intel(R) Core(TM) i5-8265U
- Claude subscription: Pro
- Claude Desktop version: latest (downloaded from claude.com/download)
Steps to Reproduce
- Install the latest Claude Desktop app on Windows with an Intel i5-8265U processor
- Log in with a Pro plan account
- Launch the application
- Observe that the Cowork tab is completely absent from the navigation
What Should Happen?
The Cowork tab should be present and accessible, as Cowork is advertised as included in the Pro plan.
Error Messages/Logs
Only the "Chat" tab is visible. No error message is displayed — the Cowork tab is simply not there. Restarting the app and the machine does not resolve the issue.
Steps to Reproduce
Cowork appears to rely on virtualization technology (similar to Hyper-V) that is not available or not supported on Intel i5-8265U processors. This hardware limitation silently prevents the Cowork tab from appearing, with no explanation shown to the user.
Additional Notes
It would be helpful if the app displayed a clear message explaining why Cowork is unavailable on unsupported hardware, rather than simply hiding the tab without any feedback. Users on unsupported hardware currently have no way of knowing whether the issue is their subscription, their app version, or their hardware.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
4.6
Claude Code Version
4.6
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗