Cursor Offset Bug in Editor (v0.48.9)

After today’s update, the cursor in the editor shows increasing offset when clicking into text.

When clicking near the beginning of a line, the blinking cursor appears in the correct position. However, the further you click from the start of the line, the more offset appears between the clicked position and the actual cursor.

Steps to Reproduce:

Launch Cursor with extensions disabled:
cursor --disable-extensions

Open an editor window.

Click at different positions on a line — offset increases with distance from the beginning of the line.

:laptop: System Info

Cursor Version: 0.48.9 (user setup)

VSCode Version: 1.96.2

Commit: 61e99179e4080fecf9d8b92c6e2e3e00fbfb53f0

Date: 2025-04-12T18:45:22.042Z

Electron: 34.3.4

Chromium: 132.0.6834.210

Node.js: 20.18.3

V8: 13.2.152.41-electron.0

OS: Windows 10 x64 (Build 19045)

The bug occured after updating cursor today.

Bug happens when clicking in an Editor-Window.
Cursor_uCumnVvNiO

Waw finally someone with the same issue as mine.
The only differences are that for me the offset is on the other side (toward the left instead of right) and that the issue is happening since an eternity… Like since the first time I tried Cursor, around one year ago to today.
And the only way to fix it (temporarily) is to hit CTRL+Shift+P and reload window.
This is such a pain I hope someone could give us a hint about that.

Okay I seem to have found a quicker temp fix, if I zoom in then out (CTRL+ + then CTRL + -).
It seem to remove the offset, but like the reload quick fix that is still temporary.
You can have a look at this post from 2024 where someone had a similar issue, maybe that could help:
https://forum.cursor.com/t/a-very-big-bug-about-cursor/18900/2

It could also be related to the font, as users have noted before.

1 Like

Good observation, I’m using JetBrains Mono, what about you @eltoro0815 ?

Consolas, ‘Courier New’, monospace

Does not work in my case

does not work in my case also

Consolas, ‘Courier New’, monospace

I installed a new Cursor on another PC.
I did a file diff with the folder C:\Users[USER]\AppData\Roaming\Cursor
I walked through the folders and files.
At the end there was only the settings.json left.

With a new settings.json the cursor bug was gone.

I added all the stuff that was general stuff, like font size, font familiy, etc.

The bug was still gone.

At the end I had some config from an extension, which caused the bug.

So what I learned from this is:

Even if you start cursor with:

cursor --disable-extensions

Extensions can ■■■■ up your editor.

But the good thing is: I have a nice editor again :slight_smile: <3