Can't re enable cursor review

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I was on the nightly release of cursor, so I saw the agent review feature early. It was not there for me yet so I checked a setting which disabled it entirely. It’s now come further and I’d like to try integrating it into my workflow again. However, this setting is no longer in the cursor app. How can I re-enable this feature?

Steps to Reproduce

  1. Go back to the initial nightly release with cursor review
  2. Update to the most recent version

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 2.4.22 (Universal)
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

hi @Mikil_Foss Agent review is in all release channels. Could you check Settings > Agents

Yes, I have this setting on. There was a different setting early called something like “enable agent review” and that was the setting I had disabled.

Hey there!

Thanks for reporting this! An early “Hide Agent Review” toggle existed in Beta settings but was removed from the UI without clearing the stored value for users who had it enabled.

To fix this:

  1. Quit Cursor completely.

  2. (Optional but recommended) Backup your database:

    cp ~/Library/Application\ Support/Cursor/User/globalStorage/state.vscdb ~/Desktop/state.vscdb.backup
    
  3. Run this command to reset the setting:

    sqlite3 ~/Library/Application\ Support/Cursor/User/globalStorage/state.vscdb "DELETE FROM ItemTable WHERE key = 'cursor/hideAllBugbotFeatures';"
    

    Note: If you get “command not found”, install sqlite3 first:

    brew install sqlite3
    
  4. Restart Cursor. Agent Review should now appear again.

We’ll raise a bug internally to add a proper migration, or just ignore this setting entirely.