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.
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.
“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.
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.
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:
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.
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.
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?
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.
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.
