[BUG]
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 main Claude Desktop window on Windows stays pinned above all other application windows. It does not behave like a standard window — when switching focus to another app, Claude remains visible on top instead of moving behind it.
What Should Happen?
Expected behavior
Claude Desktop should behave like a standard Windows/Electron window and follow normal z-order — it should be painted behind whichever window currently has focus.
Error Messages/Logs
Steps to Reproduce
- Open Claude Desktop on Windows.
- Switch focus to any other application window.
3Observe that the Claude Desktop window remains visible on top instead of moving behind the focused window..
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
unknown
Claude Code Version
Version 1.37937.3 (28dcf5)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
This is a Claude Desktop app bug, not Claude Code CLI. The main chat window on Windows stays always-on-top of other applications and doesn't drop behind them when focus switches to another app. There's no in-app setting to disable this. Minimizing the window is the only workaround; quitting and relaunching does not fix it.
Related existing reports: #85891, #87895, #88093 (Windows), #66516 (macOS counterpart).
3 Comments
This is a workflow breaking issue for me.
Use this gist to alleviate the issue without having to terminate Claude desktop at all. This keeps the app and all it's children running: force_claude_to_background.cmd.
It's a Powershell command in a CMD wrapper.
It finds the Claude process with a valid window handle and invoke SetWindowPos on it to force it to the bottom of the screen stack.
This is an absolutely brutal bug. Don't even know how a bug like this sneaks into your deployments. Please fix.