[BUG] VS Code plugin 2.0: text input UI element not recognised as an input by VS Code keybindings

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?

This VS Code keybinding should not trigger when typing inside the Claude Code prompt text input:

  {
    "key": "space a",
    "command": "workbench.view.search",
    "when": "!inputFocus"
  },

When I type something like "create a website" in the Claude CLI side panel text input, after typing a, the search panel opens up. This should not happen because the keybinding is configured to not apply when there is input focus. The text input should have input focus (and disable the keybinding) when typing in it, but it does not appear to.

This makes it almost impossible to use the plugin as I keep ending up in the search panel when I'm trying to type prompts (only if I keep my keybindings, but I'm not willing to give up my keybindings)

What Should Happen?

The search panel should not open up with typing the sequence SPACE+a into the prompt text input.

Error Messages/Logs

Steps to Reproduce

1. in VS Code, open up keybindings.json and add the following:

  {
    "key": "space a",
    "command": "workbench.view.search",
    "when": "!inputFocus"
  },

1. open the claude code plugin in the sidebar

1. Try to type "create a website" in the claude code prompt. After typing "create a " the search panel will open and steal your keyboard focus.

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

Not applicable, as the previous version did not have a GUI text input.

Claude Code Version

https://marketplace.visualstudio.com/items?itemName=anthropic.claude-code v2.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

VS Code custom keybindings.json:

[
  {
    "key": "space a",
    "command": "workbench.view.search",
    "when": "!inputFocus"
  },
]

After typing "create a" (note the "(space) key was pressed, waiting for second key of chord...")

<img width="1230" height="233" alt="Image" src="https://github.com/user-attachments/assets/f30cffd5-85e1-4d8d-863e-59bd6b5eb94d" />

... I end up in the search panel, but the the keybinding should have been ignored.

<img width="1108" height="363" alt="Image" src="https://github.com/user-attachments/assets/b93c3678-3685-4dd2-89e3-6ff7faf88180" />

Very frustrating. I do not have this issue with other text inputs in other plugins.

VS Code:

Version: 1.104.2 (user setup)
Commit: e3a5acfb517a443235981655413d566533107e92
Date: 2025-09-24T11:21:37.073Z
Electron: 37.3.1
ElectronBuildId: 12404162
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Windows_NT x64 10.0.26100