Cursor 2.3 is here!

A post was split to a new topic: What is the Windows keybinding for custom views in Cursor

Has this been shipped to all? since i’m not seeing mine getting the update

Version: 2.2.44 (Universal)
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

I am still on Version: 2.2.44 too

@sedghi @Peter_Cox

It should be rolled out to everyone soon, but you can get it now through the link!

1 Like

I got it today and I have to protest the enforced layout change. Why?? I am losing next 30 min I didn’t plan to lose because of this.

Hey @fgaletic

What changed? One of the goals for this release was no surprise layout changes.

Thanks for following up, I just clicked the update today and the Agent layout is all jumbled up - the agent pane is now back on the right side, the project tree is on the left side, files are again the focus page

image.png

Edit: fixed it by right clicking the main pane and choosing Move Primary Side Bar Right but it wasn’t obvious. Sorry for the Karening earlier, still might be an unintentional bug

1 Like

With the newest version, the go to next file moved back near the title bar from the bottom of the editor, even in editor mode. Can we please have an option to move it back down?

1 Like

just downloaded the new cursor, and it’s stuck, can’t open new chats, and sometimes cant open cursor

hi,

what happened to unlimited auto mode requests ?!! can you please hold at least 2-3 months without changing the pricing model?

My chat layout seems completely messed up all the time. There seems to be two modes of chat windows for some reason? And which form is opens seems completely random to me, often causing me to have 2 chat windows next to each other. It’s all extremely confusing and clunky. Also, having to go into a submenu to simply open the chat window or terminal is so bad in the UX department. A couple of months ago, I just had buttons there that would open those panes.

EDIT: I seem to have resolved this by setting the Default agent location to Pane. But that does mean the Editor setting there is fundamentally broken in behavior. My complaint about losing the buttons for open/closing the agent pane and the bottom pane still stand. It’s very annoying.

1 Like

I have the exact problem here. All my chats open in editor view. Not the panel itself.

From now on, ALL of your future releases should be made with the ONLY purpose to stabilize Cursor!!

NO MORE NEW FEATURES UNTIL EVERY ISSUE IS RESOLVED.

I haven’t been able to use Cloud agents for almost 3 months even though I’m paying $500 a month (2 ultra accounts + $100 of API usage)…..

And I’m VERY close to changing to Antigravity…….

2 Likes

Hey all,

The goal of this thread to is act as a place to discuss the release. Our team will probably not react to individual issue reports here.

I’m tired of creating Bug Reports that just spend months unnoticed and/or unresolved, to the point that I already gave up on signaling new issues…….

My strategy now is to remain in an old version, get used to the current issues I have, and miss all the new features you’re launching, until my patience runs out and I decide to switch to the competition…and I believe A LOT of more people are doing the same thing as me.

I upgraded to 2.3 and it was so bad and full of bugs that I needed to be reloading Cursor constantly in order to get back to a good state, losing in each reload all of my terminals’ outputs.

I degraded to 2.0 in a heartbeat.

2 Likes

After updating to 2.3, pressing apply to a worktree now makes no real changes to the file, and worktrees see tens of files as modified as only a few files are modified. They are marked as bugs 15 and 16 in my local text document of all the ways cursor has broken for me.

We really do need this. This was one of the single greatest losses with the 2.x major version. Please bring back @code.

FWIW, the experimental auto-complete in the new 2.x prompt editor is highly inconsistent. Assuming it triggers at all (which is maybe 20% of the time), it frequently does not complete most things from code. It seems largely biased to completing things from recent ā€œmemoryā€ (recent Cursor/agent content and context accessed?), but it does not work with the vast majority of code. The @code moniker brought up a proper typeahead search popup, which did seem to function across the entire codebase (in my case, I have loaded into cursor a directory which contains many individual repos, so its not a single code base).

Having to reference whole files then just text that references the part of the file you care about, usually results in higher token burn, as the agent then needs to grep and search in files to find the text you need it to reference, which isn’t always perfect, etc.

@code…definitely one of the biggest losses with 2.x.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.