Did the recent update change "Accept" to "Keep"

Describe the Bug

Did the recent update change the button label from “Accept” to “Keep”? I find the new wording a bit confusing—it’s unclear whether “Keep” refers to keeping my original code or keeping the AI-generated suggestion.

Personally, I think “Accept” was clearer and more intuitive. Just wanted to share this feedback in case others feel the same.

Steps to Reproduce

download the recent client and generate some code

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.0 (Universal)
VSCode Version: 1.99.3
Commit: 410000a83355c025daba0c6156955bf08687d080
Date: 2025-07-23T05:46:59.221Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes

Hi @billconan and welcome to Cursor Forum

Thank you for your feedback on the new UI changes.

I will pass the feedback to the team and really appreciate the details provided.

Hey, yes, exactly. Now “Keep” means the same as “Accept” did before, and it means the same thing: you either accept the changes or reject them.

1 Like

“Accept” was confusing too because it took me a while to figure out that when changes were made by the agent, the file was already saved with them even before I pressed accept. I think “keep” makes more sense, since it implies the changes have already been made.

2 Likes

@MidnightOak that’s a great point. Depending on settings for Agent especially auto run or commit this would indeed be the case.

Absolutely NOT a fan of ‘Keep’/‘UNDO’. Accept/Reject was much clearer language, and appeared in each tool call/edit, where now I need to accept in bulk or the file viewer, not progress, I consider this a regression. With no clear advantage, what else can you call it? Also, Agents now bash through endlessly w/o interruption like a bull in a china shop. Not a fan of the updates. Cancelled my subscription.

3 Likes

Let me to help with a free UX advice: let the users have an option to rename it as they want. Problem solved.

@AngryUser thank you for your feedback, we will consider it.

1 Like

I vote for Keep/Undo

Me too, but it is a very subtle thing to make someone happy. It is not like the ‘uber alles’ customizations Blender interface designers made possible for users, but a step forward how to serve users well UI/UX-related.

:ok_hand: Keep - ACCEPT
:-1: Go back - CANCEL
:hand_with_fingers_splayed: Ooopsie - ERROR!
:police_officer: Ooopsie, can’t do that - ERROR - ACCESS DENIED!
:scream: Something went wrong - UNHANDLED EXCEPTION
:skull: Whoops, missing page or content moved - HTTP/404 NOT FOUND

1 Like

“Keep” is weird terminology… are you keeping what was there BEFORE or keeping the changes? Accept was clear but also a but confusing because technically the changes were already accepted and file saved with them, and you were really deciding to undo the changes or not.

2 Likes

Correct, Keep would keep the changes, Undo would undo them :slight_smile:

2 Likes

The thing is, sometimes it deletes something, and it still says “keep”.

2 Likes

I mean you are choosing to “keep” the change, and the change could include deleting something.

1 Like

This. Keep/Undo is very confusing and not common language among any other applications or workflows. Accept/Reject are actual antonyms and made sense - you were accepting a change or rejecting it.

Between this and the new default context tab behavior it just ruined the user experience of the application for regular development tasks.

The previous way of accepting each change and showing each file was better in some ways as now it is affecting all files without interaction and they you have the option to undo…

Something broke in my Cursor UI a few days ago too… not sure I will be keeping with this. Seems CoPilot is very similar now and more acceptable to Enterprise organisations…

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