[BUG] Claude Desktop Mac - window drag area poorly positioned, making window difficult to move

Resolved 💬 3 comments Opened Apr 20, 2026 by marksnewton Closed Apr 24, 2026

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?

What's Wrong?
On macOS, the grabbable/draggable area for moving the Claude Desktop window is oddly positioned and difficult to target. It does not behave like a standard macOS title bar, making it frustrating to reposition the window when arranging it on screen.

Expected Behavior
The window should be draggable from a clearly defined title bar area consistent with standard macOS app behavior.

Actual Behavior
The drag target area is awkwardly placed, requiring excessive precision to grab the window. Typical attempts to move the window often fail or miss the grab zone entirely.

Steps to Reproduce
Open Claude Desktop on macOS
Attempt to click and drag the window to reposition it
Observe difficulty locating a reliable grab area

Platform
App: Claude Desktop 1.3109.0 (35cbf6)
OS: macOS Tahoe 26.4.1
Hardware: MacBook Air 13-inch, M4, 2025

Related Issues
#6793 (similar window draggability issue reported on Windows)

What Should Happen?

The window should be draggable from a standard macOS-style title bar region spanning the full top of the window, consistent with native Mac app behavior and macOS Human Interface Guidelines.

Error Messages/Logs

N/A — this is a UX/layout issue with no associated error or crash output.

Steps to Reproduce

Open Claude Desktop on macOS
Attempt to click and drag the window to reposition it
Observe difficulty locating a reliable grab area

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.3109.0

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗