[BUG] Ctrl+Shift+Tab is partially intercepted by Claude Code and also triggers Shift+Tab mode switching

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Description

In the Claude Code VS Code extension on Windows, Shift+Tab is used to cycle Claude Code's permission mode. However, when I press Ctrl+Shift+Tab to navigate to the previous editor tab, Claude Code also appears to consume the Shift+Tab portion of the key chord and changes its permission mode.

The result is that Ctrl+Shift+Tab performs both actions simultaneously:

1. VS Code navigates to the previous editor.
2. Claude Code changes its permission mode as though Shift+Tab had been pressed.

This is disruptive because changing editor tabs should have no effect on Claude Code's permission mode.

Environment

• OS: Windows 11
• Editor: Visual Studio Code
• Claude Code VS Code extension: 2.1.252

Important: This issue occurs in the Claude Code VS Code extension/panel itself. The terminal selection above is simply the closest available option in the issue form; the problem is not specific to shell behavior.

Related issues

This appears closely related to previously reported Claude Code issues:

• #36531 — "[BUG] Permission mode resets to different mode when switching editor tabs via Ctrl+Tab / Ctrl+Shift+Tab"
• Reports Ctrl+Tab / Ctrl+Shift+Tab changing Claude Code's permission mode unexpectedly.
• The issue was closed as not planned and marked as a duplicate.

• #24084 — "[BUG] Switching VS Code editor tabs with Ctrl+Tab changes Claude Code permission mode erratically"
• Reports similar behavior when using VS Code's editor navigation shortcuts.
• The issue was subsequently closed.

Those issues describe the broader symptom of Claude Code's permission mode changing during editor-tab navigation. This report is intended to more specifically document the keyboard handling problem with the Ctrl+Shift+Tab chord, where Claude Code appears to process Shift+Tab even though Ctrl is also pressed.

Additional note

This has been verified / reported by multiple humans. Please try to reproduce before automatic closing.

Ctrl+Tab and Ctrl+Shift+Tab are standard VS Code keyboard shortcuts for navigating editor history. Ctrl+Shift+Tab is the reverse navigation action.

This makes the behavior particularly problematic because these are fundamental editor navigation shortcuts that users may reasonably expect to work without affecting Claude Code's internal state.

What Should Happen?

Expected behavior

Ctrl+Shift+Tab should only perform the VS Code editor-navigation action.

Claude Code should ignore the Shift+Tab shortcut when Ctrl is also held.

The Claude Code permission mode should remain unchanged unless the user explicitly changes it.

Actual behavior

When Ctrl+Shift+Tab is pressed:

• VS Code navigates to the previous editor as expected.
• Claude Code simultaneously responds to Shift+Tab and changes its permission mode.

In other words, the key chord appears to be handled as both Ctrl+Shift+Tab and Shift+Tab.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce

1. Open VS Code on Windows with the Claude Code extension installed.
2. Open multiple editor tabs.
3. Open Claude Code in the VS Code panel.
4. Set Claude Code to a permission mode that makes the change easy to observe.
5. Press Ctrl+Shift+Tab to switch to the previous editor.
6. Observe that VS Code switches to the previous editor and Claude Code changes its permission mode.

For comparison:

• Shift+Tab intentionally changes Claude Code's permission mode.
• Ctrl+Shift+Tab should only navigate to the previous editor.
• The Ctrl+Shift+Tab chord should not be interpreted as Shift+Tab by Claude Code.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.252

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_