[BUG] Claude Desktop (Windows): Window control buttons overlap app UI in RTL OS language

Resolved 💬 2 comments Opened May 21, 2026 by RonGamzu Closed May 21, 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?

I am using Windows 11 Pro with the system display language set to Hebrew (RTL layout).
Because of this, Windows places the system window controls (Minimize, Maximize, Close) on the top left corner.
The Claude Desktop app places its internal navigation buttons in the exact same top-left corner. This creates a physical UI overlap, making the app's internal buttons completely unclickable.

(Environment: Windows 11 Pro Hebrew, Claude Desktop App for Windows)

What Should Happen?

The app should respect the OS window chrome and detect the RTL system layout. It should adjust its internal UI elements or top bar spacing so they do not overlap with the OS-level minimize/maximize/close buttons.

Error Messages/Logs

N/A - This is a visual UI layout issue, no error logs are generated.

Steps to Reproduce

  1. Set Windows 11 system display language to Hebrew (or any other RTL language).
  1. Open the Claude Desktop App.
  1. Look at the top left corner of the application window.
  1. Try to click the app's internal navigation buttons (notice they are physically blocked by the Windows Minimize/Maximize/Close buttons).

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.91 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Non-interactive/CI environment

Additional Information

<img width="574" height="139" alt="Image" src="https://github.com/user-attachments/assets/f14d3b7e-db72-41dc-b259-4a6fd6fc856f" />

View original on GitHub ↗

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