After upgrading to 3.5, "Review Next File" does not show until I refocus the editor

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

During a multi-file Agent review session, after I upgrade Cursor to 3.5, when I switch to another file only by changing tabs (without clicking inside the editor), the “Review Next File” button in the strip below the tab bar does not appear. It only becomes visible after I click the editor area again to give the editor focus.

Before the upgrade, when the active file changed, that button appeared immediately without needing to click the editor. This feels like a regression and makes the review flow less obvious.

Environment: Windows 10, Cursor 3.5.x (fill in exact build from Help → About).

Steps to reproduce:

  1. Start an Agent session that edits multiple files and enters the file-review flow.
  2. Use the tab bar to switch to the next file to review without clicking in the editor body.
  3. Observe: “Review Next File” is missing or not updated until the editor is clicked.
    Expected: The review banner updates as soon as the active editor / file changes.
    Actual: The banner only updates after the editor regains focus.

Steps to Reproduce

Steps to reproduce:

  1. Start an Agent session that edits multiple files and enters the file-review flow.
  2. Use the tab bar to switch to the next file to review without clicking in the editor body.
  3. Observe: “Review Next File” is missing or not updated until the editor is clicked.

Operating System

Windows 10/11

Version Information

Version: 3.5.33 (user setup)
VSCode Version: 1.105.1
Commit: aac81804b986d739acab348ed96b8bea6e83cc50
Date: 2026-05-22T06:47:48.039Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.17763

Does this stop you from using Cursor

No - Cursor works, but with this issue

Thanks for reporting this with clear reproduction steps. This is a known bug — our team is tracking it and working on a fix. The review controls have a focus dependency that prevents them from appearing when you switch tabs via the tab bar without clicking in the editor body.

For now, clicking inside the editor area after switching tabs (as you’ve already discovered) is the quickest way to trigger the controls. We know this adds friction to the review workflow, and the team is actively looking at it.

You may also find this related thread helpful: “Review next file” no longer showing