File links and review mode issue

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

File links in the agent-edited files list above the agent prompt no longer take me to the actual file. Instead I am taken to review mode.

  1. This breaks UX flow as I have to go find the real file after accepting changes
  2. There is no easy way to jump to files. I can scroll the chat looking for a code block with a link or click through modified files looking for it.

Secondary issue: I had a couple of chats loose that codeblock file list. Request ID below.

Steps to Reproduce

Ask an agent for a change and click the file link in the files list.

Expected Behavior

Take me to the file.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.26 (Universal)
VSCode Version: 1.105.1
Commit: f628a4761be40b8869ca61a6189cafd14756dff0
Date: 2025-11-24T05:39:06.655Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

GPT-5.1 at the time of the issue mentioned.

For AI issues: add Request ID with privacy disabled

38978fd8-f94c-4e99-9260-cc0313b1691f

Additional Information

I will not disable privacy, so hopefully that request id can still be helpful.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5 Likes

Previously, clicking on a file in the agent pane took you to the actual file. Now it takes you to a Review tab. Any way to set that preference?

Alternatively i could settle for a double click on filename in the agent pane.

same need this too

Hi Cursor team,

Previously, the AI agent’s Files list feature was extremely convenient. Clicking on a file would automatically take me to the exact changes in the file.

However, now when I click a file, it opens a review list instead, which is much less convenient. To see the specific modifications, I have to open the file and use keyboard shortcuts to navigate through each change.

The previous behavior—where clicking a file in the list would automatically jump to each modified location—was very efficient. I hope you can provide an option to switch back to the old behavior, as it greatly improved workflow.

Thank you!

Hey, thanks for the report.

I’ve escalated this to the team because it’s disrupting the previous convenient workflow. The old behavior (jumping directly to changes in the actual file) was indeed more efficient for many workflows.

Current workarounds:

  • Scroll through the chat to find code blocks with file links
  • Navigate through Review mode to see changes
  • Use the “next file” button on the Review bar to move between modified files
1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I can’t stand the new update where when we click on an updated file at the bottom right above the text input, it opens up the review screen. I don’t like this. I hate this. I want to go to the actual file like it did before where it would put me into the actual file. I can’t stand this review screen.

Steps to Reproduce

Obvious

Expected Behavior

It works like it did before where clicking on the updated file opens up the actual file, not the review screen.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.36
VSCode Version: 1.105.1
Commit: 9cd7c8b6cebcbccc1242df211dee45a4b6fe15e0
Date: 2025-11-26T03:43:48.079Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Somewhere this month, the option to review the code changes one by one and file by file have disappeared. Instead, I get a stacked view that does not give a clear view of the changes at all. Please bring back the previous option.

Steps to Reproduce

makes changes. Click on a file to be reviewed. A new type of review pane opens that is not usable at al..

Expected Behavior

a change-by-change and file by file review and accept/decline workflow.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.39 (Universal)
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
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

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Reported same issue, the change is annoying me too. Clicking files in chat agent which have changed should open the file, not review window

2 Likes

Nice, I was hitting this exact problem with the file links too! That solution/workaround looks spot on—finally going to give that a try.

1 Like

Yes this change is annoying af. When in the editor view, i want file links to take me to the actual file, not the review view.

Current work around: click the file link from the agent chat → get taken to the review window → click the top of the review window to go to the actual file

please fix this :slight_smile:

4 Likes

Please make this configurable, or bring back the old behavior. The review view is absolutely not suitable for working on code actively, and it completely breaks my flow. It simultaneously provides not enough context on a given file and too much context for that file - can’t easily see the whole file to get context for the changes to it, and also can’t focus on a single file in a static view because all of the changes are in one scrolling list.

This is worsened by the fact that switching between chat/agent tabs and accepting/undoing edits changes/closes review mode.

Please, please, please allow just opening files in the editor when clicking them in the edited files list.

As a side note, it seems to degrade performance even further when dealing with a large list of changed files.

3 Likes

Came here to add more support for making this configurable. This new flow completely breaks the workflow for incremental changes as part of a larger feature. After almost two weeks, it’s still slowing me down every day.

If you’re going to change core behaviors like file-click navigation, please make it configurable. This kind of unannounced UX shift risks alienating long-term users who depend on Cursor’s speed and predictability.

1 Like

The most annoying update recently. Looking forward for it being changed back, or at least make it configurable.

any update here?