Inline assistant text written backwards

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Whenever I do Ctrl + K to pop up the in-line assistant I get this random “backward” writing. It is not a visual bug, as the assistant does not understand and sometimes answers a similar nonsense.

Steps to Reproduce

I cannot even fully describe what is going on, as english is not my first language. It mostly happens when I use double windows (separate tabs from main session).

I am constantly working with jupyter notebooks. I know the suport for .ipynb is horrible, so it might be related.

Expected Behavior

I should be able to write logical text, flowing from left to right as most english writting flows.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.4.37 (user setup)
VSCode Version: 1.105.1
Commit: 7b9c34466f5c119e93c3e654bb80fe9306b6cc70
Date: 2026-02-12T23:15:35.107Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.22631

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. That’s a really weird case. From the screenshot, it looks like the text in the input field is completely flipped.

A few questions to help narrow this down:

  1. Does this happen only in .ipynb files, or also in regular files like .py, .js, etc.?
  2. Does it happen only when the editor is split, or can you reproduce it in a single editor tab too?
  3. If you close all split panes and open a new .py file, does Ctrl+K work normally?
  4. Do you have any extensions that might affect text direction or input handling?

Also, try restarting Cursor and testing in a normal Python file without split editors. That’ll help confirm whether it’s tied to Jupyter or to split panes.

Let me know what you find.

It seems in only happen when the editor is split, in both .ipynb and .py files. Have not been using other languages recently.

I do not have text direction or input handling extentions.

1 Like

I also have this bug - also using split screen (or rather the file I’m editing is in a separate window/on different monitor to the main cursor window)

I’m editing cs files - moving the file back to the main window fixes the issue; looks like its an issue with files moved into separate windows