[BUG] [BUG] Claude Code Desktop Code tab crashes silently on Windows (Surface Pro 11, ARM/Snapdragon) after update to v1.3109.0
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?
Claude Desktop version: 1.3109.0
Windows version: Windows 11
Hardware: Surface Pro 11 (ARM/Snapdragon)
What's wrong:
Clicking the Code tab causes the window to crash silently with no error message. Chat and other tabs work fine. Only the Code tab crashes.
Steps to reproduce:
- Open Claude Desktop
- Click the Code tab
- App crashes immediately with no error code
What I've tried:
- Fully quit and relaunched the app
- Signed out and back in
- Reinstalled Claude Desktop
- Rolled back Claude Code CLI to v2.1.84 via npm
- Removed duplicate npm installation (had both npm and native installs)
- Updated to v1.3109.0 (the supposed fix)
- Issue persists after all of the above
Note: The v1.3109.0 fix appears to have resolved this for macOS users but the issue persists on Windows ARM (Surface Pro 11/Snapdragon).
CLI works fine. Only the Desktop app Code tab is affected.
What Should Happen?
Should not exit when I enter Code. Chat works fine, but it should not silently crash and exit in Code.
Error Messages/Logs
It's a silent crash or exit from Code, no error codes are given.
Steps to Reproduce
I go into Claude desktop. Chat works fine. I go into Clause Code, and it silently exits without a error code or warning. If I go back into Clause Desktop and switch to Chat, it will crash one more time. Then if I go back in and stay in Chat then it won't crash. But it crashes silently in Code
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.3109.0
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗