Next file button

Feature request for product/service

Cursor IDE

Describe the request

Please bring back the ‘Next file’ button when reviewing changes made by the agent. I prefer to choose the order in which I review changes - based on business logic and not in random order. I know I can select a file in the agent’s chat, but it’s less convenient than scrolling through files with the ‘Next file’ button.

PS: It’s sad, but I don’t follow Cursor’s UX changes at all.

Are you referring to this or something else?

image

And I agree, the constant UX changes drive me crazy.

Kind of. I don’t use the agent layout - I only work in the edit layout. After today’s update, it’s no longer possible to scroll through files. I’ll send a screenshot later.

I am in Editor Layout. I can’t get the keep/undo buttons to appear not at the top anymore. Used to before last update.

Try Cmd + E once or twice if you are on Mac. It solves this issue for me.

That did it for me. Thanks. Ctrl + E for windows.
I pressed the shortcut until I saw the double arrows in the top right.

image

It appears to be this shortcut.

Now my undo/keep buttons are behaving as an overlay again. It looks different after the most recent update, but I am seeing a button for going through the files. Is this what you are seeing?

image

I was able to also get this behavior by disabling breadcrumbs:

But now I see what you mean, I don’t have the next file UI despite multiple files being changed.

image

How can cursor’s UI be so convoluted. When I see this I have to press Ctrl+E, then it appears. But then my chat history panel no longer works.

image

Exhausting to maintain a stable UI experience.

I was wrong - the buttons are still there, but the current flow is inconvenient. When you accept or reject changes, the toolbar changes to:


When you press the button, you get back to the normal toolbar:

I believe the UX has changed compared to the previous version. I would prefer that the file switcher stays, instead of a new button that breaks the UX flow.

Hmm, what was the point of this change? At first I thought this might’ve been done as part of a way to solve the issue of accidental double click on “Keep All” where the next file in review’s “Undo All” gets shifted where “Keep All” was which is bad UX… but no, that’s still an issue.

It appears that Cursor has two Editor modes, and is trying to phase out the old one with the Next File button, since you can only switch back to it with the Ctrl+E shortcut. If you ever click on the double-arrow button to enter Agent Mode, the settings button only lets you switch between that and their new Editor Mode, which does not have the Next File button. PLEASE PLEASE PLEASE Cursors devs do not remove the old Editor mode… reviewing changes per file, in context, is crucial to our usage.

You can still review changes per file in context in the new editor mode. The undo/keep buttons and next file buttons are just in the breadcrumbs area instead of overlay. It is not my preference, so I stay on the old editor, but the functionality in the new editor is not lost. I do wish they would maintain the old editor because I do prefer it.

Old editor (overlay):

New Editor (breadcrumb):

As you can see, they both have UI for navigating to the next file.

If you are not on a file that is part of the changes, then both show a button to “Review next file”

The breadcrumb buttons in the new editor are technically better, since they are not center aligned, so the undo and keep buttons don’t move around causing you to accidentally click the wrong one.

Thanks I missed that completely! It’s hard to unlearn where to look for things. Given how important those functions are I too prefer keeping them in the bottom-centered overlay. Maybe Cursor can allow for that in a sub-option when they fully deprecate the old Editor Mode (and preserve if the user is in the old Editor Mode, which they’re using now to show the double arrow button)

I thought it was my settings that caused this problem. It turned out that cursor completely abandoned the original layout and placed this option in the upper right corner. I am not used to this method and I really hope they can keep the two modes and switch between them. Of course, if my understanding is incorrect, you can switch to the old layout. Please tell me how to do it, thank you.

Ctrl + E (windows), Cmd + E (mac).

You will see this double arrow in the top right when you are using the older editor layout where the undo/keep buttons are overlayed in the center.

image

I have the overlay at the bottom and I WANT the buttons at the top… but there is no way to achieve this. No amount of cmd-E switching gets my review buttons in the top bar instead of overlay.

I hate the overlay because it moves the undo button under mouse click on last file so its really easy to click it accidentally. Much preferred the top version, but now automatically went back to overlay.

Can there not be a simple setting for users to choose where the review buttons appear (topbar or overlay)….

Yea, just as I got used to the buttons being at the top they are now ALWAYS at the bottom/overlay. I could not find a way to get them back in the top breadcrumbs area. This is so dumb. First they force us to get used to the buttons in a new place for weeks, then revert it back, forcing us to get used to it there.

And yes, the breadcrumbs location is superior because you don’t accidentally hit the undo button which is so annoying.

Submitted bug report here:

As of today’s update I can no longer see the undo/keep buttons as an overlay, even with Ctrl+E. They are ONLY in the breadcrumb area. This is a very destructive action for someone who’s only ever used the Editor-overlay mode of Cursor. I would personally like to see their location as an option, because in the breadcrumb bar they are now tiny and non-obvious, and I never had a problem with accidental undos.

They developers said they only wanted to maintain one editor layout, not the classic and current. The classic used to be toggleable with Ctrl+E, but they have gotten rid of it entirely and decided to make the breadcrumb buttons the only location. They said they may make it a setting to make the buttons overlay, but I would not count on it. The direction seems to just standardize the editor and make it more and more like a vibe code editor.

This is too bad. After a year of Cursor I decided to try out everything else like Claude Code and Codex. I switched back after a month because they were really only servicing a true vibe coder instead of the hybrid workflow I need as a software engineer.

@BE-Code I switched to Claude Code (terminal) + VS Code + Copilot (mainly for tab autocompletion and small tasks). I’m not going to say that I will never come back, but so far I am absolutely happy with the max Claude Code subscription. What can Cursor do that Claude Code cannot? I am really very interested in your opinion, so I would greatly appreciate your response.

It is mostly workflow things.

  1. Tab completion. You use another tool to fill that need, but it is lacking in Claude Code. I don’t know how good Copilot’s is, but I feel like Cursor’s adapts very quickly to recent edits, so if you are making a similar refactor in several places the suggestions get really good after the 1st/2nd one.
  2. Cursor saves the changes before you accept/reject them. This allows you to test the result before accepting it.
  3. Ability to edit before accepting. You can tweak the code in the diff before accepting.
  4. Accept/Reject at the block level. More granular control over the changes it makes.
  5. Better keybindings to reference multiple blocks of code from different files in one prompt.
  6. The result of 2-4 is that you don’t have to use git to juggle ai changes while you are testing its code. You use the built in diff and tweak it and re-prompt until everything is working correctly, then you accept. This frees your staging area to be used however you’d like.
  7. This may just be personal experience or a configuration issue, but I feel like Cursor’s index gives it a better grasp of the codebase. Claude was always grepping around trying to find the relevant files, and it would often give me incomplete fixes like making all the right changes to the backend, but ignoring the frontend. I haven’t had that problem with Cursor. The changes it makes consistently change everything that would be affected.