Editor in a new window, zoomed in, typing from right to left

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Due to poor font size of the editor(agent)/scaling settings, I spent some time trying to get the text size I want with workarounds. Started to consider that the only way to use Cursor’s agent with a proper text size would be in a new window, zoomed in once, with some specific values of the text in the settings. I was fine with that until I noticed that after a few prompts (sometimes it happens just to be 1), the editor is starting typing backwards, from right to left. Also, functions like ctrl+A don’t work anymore, in short terms, the editor text-input becomes unusable. I would really like more text sizes in the settings panel, as 4 text sizes for the editor are just not sufficient, or this bug fixed, as I don’t mind using it like this.

Steps to Reproduce

Open Cursor. Ctrl+L to open the AI agents. Right click on the AI agent tab, choose ‘open as Editor’. From the new pop-up, right click on the editor tab and choose ‘open in a new window’. ctrl + ‘+=’ once and then do prompts. at some point, it starts typing backwards.

Expected Behavior

to not start typing backwards or better, some more options about scaling/text in the IDE itself, as a better customisation for that is not much to ask.

Operating System

Windows 10/11

Version Information

Version: 2.6.20 (system setup)
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

I was using Sonnet 4.6 when I encountered the bug, but it also happened for Opus 4.6

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, this is a known issue. Chat in a separate window can be unstable right now because of multi-window rendering limits. Backwards typing and Ctrl+A not working are part of the same bug.

Workaround: after you open chat in a new window, press Ctrl+Shift+P, type Developer: Reload Window, then press Enter. This temporarily fixes typing. You may need to repeat it if it breaks again.

For font size, try editor.fontSize in settings.json and window.zoomLevel for overall zoom. It’s not perfect, but it can help you avoid using a separate window.

The team knows about the issue, and your report has been added. Let me know if the workaround helps.

6

“window.zoomLevel” in settings.json seems to be a convenient workaround for me. I didn’t know it was a known issue, didn’t get the time or the chance to look through the forum’s bugs, as it was the only I encountered so far.
Other than that, thank you for your quick reponse. Appreciate it.

7

Glad window.zoomLevel works for you! If the backwards typing issue comes back in any other scenario, feel free to report it here. We’re tracking this one.

8

Got same issue. Any plans on fixing this?

9

Hey, this is a known issue. Text input can switch to right-to-left when the chat is opened in a separate window. It’s related to multi-window rendering limits.

Two workarounds:

  1. If you already opened it in a separate window, press Ctrl+Shift+P, type Developer: Reload Window, then press Enter. This should temporarily fix typing.
  2. Instead of using a separate window, try setting window.zoomLevel in settings.json to get the zoom you want. The issue doesn’t happen there.

The team knows about the bug. There’s no ETA for a fix yet, but each report helps with prioritization. Let me know if the workaround helps.

10

image
image2750×1426 413 KB

Workaround 1 doesn’t seem to work (see screenshot - it removes the separate editor agent window and puts it back into the main code area).

Workaround 2 - this is not a zooming issue at all (?)
Like, I’m not using a separate window to make the text bigger. I’m using it because it’s a lot easier to have it on the left in a separate window (rather than taking up space in the main code editor)

”The team knows about the bug” - how is there no ETA for a fix on this rather large bug?

Can’t you guys just use AI to fix this? :see_no_evil_monkey:

11

Hey, I see the screenshot. Yeah, running Developer: Reload Window in the separate window does move the chat back to the main window. That workaround won’t work for your setup.

And you’re right, it’s not about zoom. Using chat in a separate window on a second monitor is a totally reasonable workflow. Sadly, there isn’t a proper workaround for this case yet. The bug is related to how the Lexical editor used for chat input initializes in auxiliary windows. Focus events behave differently there, and typing breaks.

The team is aware of the issue. No ETA yet, but every report helps with prioritization, and I’ve added yours.

Let me know if you find any workaround on your end, and we’ll add it to the thread.

12

No workaround (other than clicking in the textarea and holding the mouse down which is painful). If this bug can be resolved soon it would make this product a whole lot better as it’s a major pain having to copy and paste from a text editor each time.

Thanks for adding the issue to the prioritizations much appreciated.

13

As part of this issue: Pasting in text and then pressing backspace (DEL on mac), causes mouse cursor to move to the very start of the text input :see_no_evil_monkey:

14

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The text gets mirrored when I type in an agent tab that’s in its own window. For example, ‘Hello’ becomes ‘olleH’. I’ve found a manual fix: if I type the first letter and then click right after it, it starts working correctly. It seems like the cursor automatically jumps back to the start of the text box when I type directly.

Steps to Reproduce

Open the IDE and create a new agent. Drag the tab outside the editor to open it in its own window. Click out of the agent’s text box, then try clicking back in.

Screenshots / Screen Recordings

Screenshot_1.png
Screenshot_1.png1012×443 6.29 KB

Operating System

Windows 10/11

Version Information

Version: 3.0.16 (user setup)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

The text box behavior is also glitchy when deleting letters; it often snaps back to the beginning of the line or the first character.

Does this stop you from using Cursor

No - Cursor works, but with this issue

EDIT (added recording):

15

Any word on this?

More folks experiencing same issue:

16

Any update on this?

Installed latest update and still this issue remains … [sadness]

17

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using the Agent within the Cursor editor, the text cursor consistently and unexpectedly jumps to the beginning of the current input/line. This happens during normal typing and when using the Backspace key, resulting in text being inserted backwards.

Important Discovery: This bug is strictly isolated to when the Agent is popped out into an independent/floating window. If the Agent is docked in the main window, typing functions normally.

Steps to Reproduce

  1. Open Cursor.

  2. [CRITICAL STEP] Pop the Agent out into a separate, independent window. (see attached screenshot showing the “Agents Window”)

  3. Focus the input field in this separate window and attempt to type the word cat.

  4. Type c. The cursor immediately jumps to the far left: |c.

  5. Type a. Because the cursor is at the beginning, it inserts before ‘c’, resulting in |ac.

  6. Type t. The final text becomes tac instead of cat.

  7. Alternatively, place the cursor at the end of a word and press Backspace. The cursor immediately relocates to the far left instead of deleting the previous character.

Expected Behavior

The text cursor should maintain its correct position relative to the user’s input, even when the Agent is operating in a separated window.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.2.11 (system setup)
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Yes - Cursor is unusable

18

Any updates on this? Still a major issue