Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix VS Code: Add setting to open review diffs in active editor group instead of split [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55525•Fetched 2026-05-03 04:51:06
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
ndomanovskiyndomanovskiy
Participants
github-actions[bot]github-actions[bot]ndomanovskiyndomanovskiy
Timeline (top)
labeled ×3commented ×1

Root Cause

This is problematic because:

  • On small screens or laptops, the split makes both panels too narrow to read comfortably
  • Users who prefer a single editor group workflow are forced into splits they didn't ask for
  • There's no way to configure this behavior — neither in the extension settings nor in VS Code's built-in settings
RAW_BUFFERClick to expand / collapse

Problem

When Claude Code opens a review/diff view (e.g., plan approval, proposed file changes), it always opens in a new editor group (split layout), creating an unwanted split.

This is problematic because:

  • On small screens or laptops, the split makes both panels too narrow to read comfortably
  • Users who prefer a single editor group workflow are forced into splits they didn't ask for
  • There's no way to configure this behavior — neither in the extension settings nor in VS Code's built-in settings

Current behavior

  1. User is working in a single editor group with Claude Code open as a tab
  2. Claude Code triggers a review (plan approval, diff view, etc.)
  3. The review opens in a new editor group to the right (or bottom, depending on workbench.editor.openSideBySideDirection)
  4. Screen is now split — user has to manually close the extra group every time

Expected behavior

A new extension setting (e.g., claudeCode.reviewLocation or claudeCode.openDiffsInActiveGroup) that allows users to choose:

  • "beside" (current default) — opens review in a new editor group
  • "active" — opens review in the current/active editor group as a regular tab

Technical context

The extension uses ViewColumn.Beside when calling vscode.diff or createWebviewPanel for review views. The fix would be to check a configuration setting and use ViewColumn.Active instead when the user prefers it.

Similarly, createPanel() in the extension defaults to ViewColumn.Beside for new Claude Code tabs. The claude-vscode.primaryEditor.open command already supports ViewColumn.Active — this behavior should be configurable as the default.

Environment

  • VS Code on Windows 11
  • Claude Code extension v2.1.83

extent analysis

TL;DR

To fix the issue, the Claude Code extension needs to introduce a new setting that allows users to choose where review views open, using ViewColumn.Active instead of ViewColumn.Beside when preferred.

Guidance

  • Introduce a new configuration setting (e.g., claudeCode.reviewLocation) with options for "beside" and "active" to control where review views open.
  • Update the extension to use ViewColumn.Active when the user prefers to open reviews in the current editor group.
  • Modify the createPanel() function to respect the new configuration setting for default behavior.
  • Test the new setting with different workbench.editor.openSideBySideDirection configurations to ensure compatibility.

Example

// Example of how the new setting could be used
const reviewLocation = vscode.workspace.getConfiguration('claudeCode').get('reviewLocation');
if (reviewLocation === 'active') {
  vscode.diff(uri1, uri2, 'Review', { viewColumn: vscode.ViewColumn.Active });
} else {
  vscode.diff(uri1, uri2, 'Review', { viewColumn: vscode.ViewColumn.Beside });
}

Notes

The solution requires modifying the Claude Code extension, which may involve updating its internal logic and configuration handling. This fix assumes that the extension's architecture allows for such modifications without significant side effects.

Recommendation

Apply a workaround by modifying the extension to include the proposed configuration setting, allowing users to choose where reviews open, as this directly addresses the reported issue and provides a flexible solution for different user preferences.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

A new extension setting (e.g., claudeCode.reviewLocation or claudeCode.openDiffsInActiveGroup) that allows users to choose:

  • "beside" (current default) — opens review in a new editor group
  • "active" — opens review in the current/active editor group as a regular tab
#LLM response#prompt template#agent execution#callback error#memory management

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING