Inline editing broken in 2.1.34 on MacOS Tahoe

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Version: 2.1.34 (Universal)
VSCode Version: 1.105.1
Commit: 609c37304ae83141fd217c4ae638bf5321856500
Date: 2025-11-25T16:35:52.391Z (8 hrs ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

I reverted back to 2.0.77, which was ok.

Current download is https://downloads.cursor.com/production/609c37304ae83141fd217c4ae638bf532185650f/darwin/universal/Cursor-darwin-universal.dmg but I can’t figure out how to go back to 2.1.33 again.

Cheers,
Nigel

Steps to Reproduce

Update to latest version, restart Cursor.
Prompt in agent mode with YAML file (or any other file) open.
No inline edits appear but YAML file has changed. You can switch to “diff” mode to see the edits instead.

Expected Behavior

Should prompt inline edits for approval/rejection.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.34 (Universal)
VSCode Version: 1.105.1
Commit: 609c37304ae83141fd217c4ae638bf5321856500
Date: 2025-11-25T16:35:52.391Z (8 hrs ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

For AI issues: which model did you use?

Agent, with auto mode

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

I updated ~/Library/Application Support/Cursor/User/settings.json to prevent auto-updates too

{
    "update.mode": "none",
    "update.enableAutoUpdate": false
}

See How do I prevent automatic updating?

3

Hey, thanks for the report. It looks like this is related to a known review system bug that the team is already tracking. In your case it’s a bit different though: the review panel doesn’t appear at all, while in most reports it appears but then becomes unresponsive.

To help us investigate your specific case, could you please share:

  • Console errors: open Help > Toggle Developer Tools, reproduce the issue, and take a screenshot of any errors in the Console tab
  • File types: does this happen with all files or only with YAML?

For now, the workaround is to use diff mode (which you’ve already found) or review changes through Git.

Staying on version 2.0.77 with the auto-update settings you’ve configured is a good approach until this is fixed.

4

I’ve been on 2.0.77 most of today but now I have starting up v2.1.34 (separate /Applications install) and it is working again. Very strange.

I’ll check the developer tools and see if I can reproduce it again.