[BUG] New Session button completely unresponsive in Claude Code Desktop on Windows 11
Status Open
Maintainer reply ✓ Yes — amorriscode
Activity 3 comments · opened May 20, 2026
💡 Likely answer: A maintainer (amorriscode, contributor)
responded on this thread — see the highlighted reply below.
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.8089.1 (b98a06)
Windows 11
“New session” on Code Tab has no effect and no Event Viewer errors.
No effect means there is no ask about folder for project files.
I can see only previously started sessions.
What Should Happen?
It should ask for folder to project files i think
Error Messages/Logs
Steps to Reproduce
Open Claude Desktop (1.8089.1) on windows 11, switch to "Code" tab, click on New session
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.8089.1 (b98a06)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
_No response_
3 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
taking a look
[BUG] "+ New" button unresponsive in Claude Code Desktop's Code tab on macOS
Summary
The "+ New" button in the Code tab's sidebar does nothing when clicked — no new session is created, no folder picker appears, and there's no visible feedback or error. The ⌘N keyboard shortcut also has no effect.
Environment
Steps to reproduce
Expected behavior
Clicking "+ New" (or pressing ⌘N) should prompt for a project folder and start a new session.
Actual behavior
Button and shortcut are completely unresponsive. Existing sessions in the sidebar still open and work normally.
Troubleshooting already tried
Notes
This appears related to existing reports of the same symptom on Windows 11 (see #60855 and the duplicate #50388), but no macOS report currently exists. Filing separately since the affected platform differs.