Settings Changes Don't Save on /dashboard/settings (Profile Picture & Public Profile)

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

On the https://cursor.com/dashboard/settings page if you go to remove profile picture or toggle on public profile it appears as though it saves automatically but it doesn’t and there is no save button.

Steps to Reproduce

Navigate to Settings

Go to https://cursor.com/dashboard/settings

Test Profile Picture Removal

Locate the profile picture section
Click “Remove profile picture” (or similar option)
Observe that the change appears to save automatically (no visible error)
Reload the page
Expected result: Profile picture should remain if it actually saved
Actual result: Profile picture is still there (change didn’t save)

Test Public Profile Toggle

Locate the “Public Profile” toggle switch
Toggle it ON (or OFF, depending on current state)
Observe that the change appears to save automatically
Reload the page
Expected result: Toggle state should match what you set
Actual result: Toggle reverts to previous state (change didn’t save)

Expected Behavior

Either the changes should persist after page reload, OR there should be a visible “Save” button and/or an error message indicating the save failed.

Operating System

Linux

Version Information

This is on the website so this doesn’t apply.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @AndrewSalzer!

For me, the save button appears down here. Do you see the same?

I do not. I tried changing themes/appearance as well. Toggled off public profile and removed image to try and get it to show up.

Odd! Can you share some details about your system / browser (+ version)?

Yeah it’s really weird. I can’t figure out what is causing it. Linux Ubuntu 24.04.4 LTS. Google Chrome Version 149.0.7827.53 (Official Build) (64-bit).

Let me know if there is anything else you need. I also tried logging out and logging back in and that didn’t work either.

EDIT: I fixed it by logging into an incognito browser. Hard refresh/reload didn’t fix issue on main browser.

I should mention that even after it being fixed on incognito browser it’s still broken on main browser.