Chat input characters reversed after undocking Ctrl+L panel to another monitor (classic + WSL)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Chat input characters reversed after undocking Ctrl+L panel to another monitor (classic + WSL)
Where: Editor Window (cursor --classic .), Remote-WSL

Steps to Reproduce

From WSL: cd to a project, run cursor --classic .
Confirm status bar shows WSL: …
Open chat with Ctrl+L
Drag the chat panel onto a second monitor (undock / separate window)
Type a normal message (e.g. Do you hear me?)

Expected Behavior

Expected: Message shows and is sent LTR as typed.
Actual: Bubble shows character-reversed text (e.g. ?em raeh uoy oD). The model also receives the reversed string.

Operating System

Windows 10/11

Version Information

Version: 3.15.6 (system setup)
VS Code Extension API: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

image
image1328×1399 98.8 KB

I typed LTR and yhis was the result

6

Hey, thanks for the detailed report and the screenshot. I can see the reversed text in the input, so the issue is clear.

This is a known issue with the chat panel when it’s detached into a separate window on another monitor. The caret jumps to the start of the line, so each new character gets inserted at the beginning, which makes the text appear reversed. WSL and --classic aren’t related. It repros without them too.

Workaround until it’s fixed:

  • In the detached window, press Ctrl+Shift+P, then run Developer: Reload Window. After a reload, typing in that window usually works normally again.
  • Or keep the chat docked in the main window, where the issue doesn’t happen.

I can’t share an ETA yet, but we’re tracking this issue. If there’s an update, I’ll reply in the thread. Let me know if the reload helped.