[FEATURE] Add setting to suppress file reveal when extension applies edits

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 25, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When Claude Code applies edits to a file via the VS Code extension, the file is automatically opened and revealed in the editor every time. There is no way to suppress this. Users who keep the Claude chat panel in an editor group (rather than the side panel) are interrupted on every edit — the edited file opens on top of the chat session they're actively reading, breaking focus and requiring manual tab management after each tool call.

Proposed Solution

Add a VS Code extension setting (e.g. claude-code.revealEditedFiles) that controls whether files are opened/revealed when the extension applies edits. When set to false, edits apply silently without changing editor focus or opening new tabs.

Alternative Solutions

Claude Code: Lock Editor Groups is already enabled but does not prevent the programmatic reveal. The accessibility.openChatEditedFiles setting (VS Code built-in Chat) has no effect on Claude Code's behavior. Floating the chat panel into a separate window is a workaround but impractical for day-to-day use.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

User has the Claude Code chat panel in the right editor group and source files in the left. Claude applies an edit to a file — the file immediately opens on top of the chat panel, hiding the conversation. User has to close the tab to continue reading the response, then repeat this for every subsequent edit in the same session.

Additional Context

_No response_

View original on GitHub ↗