RevealIfOpen setting is still ignored

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

As was reported about 3 months ago, the RevealIfOpen setting in VSCode is broken in Cursor. This is a major nuisance when working with files in multiple groups, leading to duplicate editors open on the same file.
Reportedly this was broken during changes back in Cursor version 2.6.
Please could this be fixed as soon as possible.

Steps to Reproduce

With the VS Code setting “Workbench > Editor: RevealIfOpen” checked, and with more than one group of editors open (and an editor in one group selected), in the Explorer click or double click on a file on which an editor is already open in another group (which is not selected). This incorrectly opens another editor on the same file in the group in which an editor is already selected. This leads to multiple editors being open in different groups on the same file.

Expected Behavior

This should select the editor which is already open on that file in the other group.

Operating System

MacOS

Version Information

Version: 3.7.42
VS Code Extension API: 1.105.1
Commit: 5702c9cfca656d8710fad58402fe37f14345e3a0
Date: 2026-06-15T19:39:42.738Z
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
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

This is a confirmed bug on our end, not your configuration. A change to how the file Explorer targets editor groups (introduced in the 2.6 series) bypasses workbench.editor.revealIfOpen, so clicking a file that’s already open in another group opens a duplicate in the active group instead of revealing the existing tab. It’s a known regression our team is tracking, and it’s still open.

There’s no setting that fully restores the old behavior yet. The cleanest way to avoid the duplicate in the meantime is to switch to the group where the file is already open rather than re-opening it from the Explorer:

  • Cmd+1 / Cmd+2 / Cmd+3 … to focus a specific editor group
  • Ctrl+Tab to cycle through open editors

I don’t have a timeline to share, but I’ve made sure your report is attached to the existing tracking issue so it’s reflected in prioritization. I’ll follow up here once there’s progress.

8

Thank you for describing this and adding to the information which affects its prioritization.
While I, like many others I presume, use Cursor for the things which it adds to VSCode, we don’t expect things to be taken away!