[Desktop App / Windows] Dragging panel headers moves entire app window instead of panels
Status Closed — not planned
Maintainer reply None cached
Activity 7 comments · opened Apr 15, 2026 · closed Jun 21, 2026
Description
On the Windows desktop app, dragging panel headers (Tasks, Plan, Terminal, etc.) moves the entire application window instead of repositioning the panel within the app layout. On macOS, panels can reportedly be dragged and rearranged as expected.
Steps to Reproduce
- Open Claude Code Desktop App on Windows
- Open any panel (Tasks, Plan, Terminal, etc.)
- Try to drag the panel by its header to reposition it
Expected Behavior
The panel should be repositioned/rearranged within the app layout (as it works on macOS).
Actual Behavior
The entire application window moves, as if dragging the app's title bar. The panel itself does not move or reposition within the layout.
Environment
- OS: Windows 11 Pro 10.0.26200
- App: Claude Code Desktop App (latest)
Notes
This appears to be a platform-specific issue where the panel header drag event is being captured by the window's drag handler (likely an Electron --webkit-app-region: drag conflict) instead of the panel layout system.
7 Comments
Just opened Claude Code on desktop for the first time, and immediately hit this bug. Unsure how this has been up for 3 weeks and hasn't been fixed?
Edit: I disabled Window's native snapping feature, and it still doesn't work. It doesn't trigger the snap functionality, but you still can't actually move the windows around.
Edit 2: Okay, so you _can_ actually move them around, but the target area to trigger it is super tiny, at the _very_ top of the window, and at the _exact_ center. If you're not in the exact center, exact top, it doesn't work. Poor UX, hope that's fixed soon.
(Update) I had Claude Code dig into the DOM and it found what looks like the cause. I'm not an engineer myself, so please correct anything I've gotten wrong.
claude.ai/code contains 5 invisible overlays with
class="draggable absolute inset-0 -z-[1]"and-webkit-app-region: drag. They cover the full width of each panel header and the top of the main pane.-webkit-app-regionis a no-op, so the JS pointer-event drag handler runs and panels rearrange normally (I confirmed they do rearrange when dragged in claude.ai/code).-webkit-app-region: dragbefore pointermove reaches JS, so the JS handler never runs and Windows treats the gesture as a window drag instead.@Tuggl3s's "only the very top center, in a tiny area" observation comes from the same overlays: only the main-pane background overlay (694×32) gives a reasonably wide drag zone; the other four sit on panel headers crowded with buttons and title text, leaving only thin gaps between the no-drag children.
The fix would be to drop
-webkit-app-region: dragfrom thedraggable absolute inset-0 -z-[1]overlays, or make it conditional on a non-Electron environment, and instead use the standard Electron pattern offrame: falseplus a single explicit drag region in the window's top chrome.Verified on: Microsoft Store Claude v1.5354.0.0 / Windows 11 Pro 26200.
There is zero visual indication of where you need to put your mouse to move the pane. Unless you get lucky and just happen to have your mouse pass over the right spot, you will never find it in the app on your own. So while theoretically the feature exists, I doubt many find it. I only found it because I'm reading through the entirety of the claude code documentation systematically.
Also, If you close the pane, the position is reset, which removes much/most of the utility of the feature.
Arrange things the way I want them, and the moment I hit a shortcut to toggle the pane, it moves right back to the original position...
And the order the panes are displayed also jumps around depending on the order in which you toggle them. So depending on the order Files turn up either above or below Diff etc...
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
This is STILL an issue... why is it closed and not planned? Extremly annyoing! Please fix!
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.