Title: Windows: TUI keybindings only work with the English keyboard layout #55371

Activity

1. opencode-agent commented on Oct 14, 2026

   

   opencode-agentBot

   on Oct 14, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the clear report! One detail is missing before we can try to reproduce this: which terminal are you running OpenCode in? For example Windows Terminal (and its version), the classic console window (conhost), WezTerm, the VS Code integrated terminal, etc. PowerShell is the shell, but the terminal is what matters here.

   OpenCode v2 can fall back to the physical key for non-Latin layouts, but only if the terminal reports the base-layout key (through the Kitty keyboard protocol). So whether this works depends on the terminal. If you can, please also say whether other shortcuts that use a letter key (for example Ctrl+C) work while the Russian layout is active.

   You can reply here with the details or edit the issue. If you edit it, please also leave a short comment saying you've updated it, so we know you're done.

   These related issues may help. The list is ordered by likelihood, most likely first:

   • Hotkeys don't work if the keyboard layout isn't english (or similar latin alphabet layout) #6364: shortcuts don't work with a Cyrillic (Ukrainian) layout (older, closed as stale)
   • bug(tui): Keyboard shortcuts don't work with Korean IME active #21163: keyboard shortcuts don't work with a Korean input method active (same kind of problem, different language)
   • [Bug] Keyboard shortcuts don't work when Chinese IME is active #24192: keyboard shortcuts don't work with a Chinese input method active
   • Keybind Ctrl + . does not work with non-US keyboard layouts (e.g., Russian) #40048: Ctrl+. doesn't work with the Russian layout (v1 desktop app)
2. opencode-agent

   added

   triaging

   on Oct 14, 2026
3. ahsan-python commented on Oct 14, 2026

   

   ahsan-python

   on Oct 14, 2026

   More actions

   can i help ### Root Cause Analysis

   This issue occurs because the TUI keybinding handler is likely evaluating input events based on decoded character streams (runes / localized string values) rather than physical Virtual Key Codes (VK codes) or scancodes.

   When switched to the Russian layout, pressing the physical B key emits its Cyrillic equivalent (e.g., и). Because the secondary sequence listener specifically expects the ASCII character b (byte 98) rather than the physical key mapping, the keybinding fails to trigger.

   The initial modifier step (Ctrl+X) works because standard control modifier sequences bypass character mapping and directly pass the control code, but the subsequent raw letter input is affected by the active layout.

   ---

   Suggested Fix & Implementation Strategy

   Depending on the underlying event handling layer used by the CLI/TUI:

   1. Physical Key/VK Code Binding (Recommended for Windows):
      Instead of listening for string/character values, bind shortcuts to physical key events or low-level Virtual Key Codes (e.g., VK_B on Windows). This ensures keybindings remain layout-agnostic and respond strictly to the physical key position.

   2. Cyrillic-to-QWERTY Mapping Fallback:
      If switching to VK code listening requires breaking architectural changes, implement a layout normalization fallback layer in the keybinding interceptor that maps Cyrillic characters back to their QWERTY physical equivalents when evaluating shortcut triggers:

      // Example fallback mapping for QWERTY <-> Russian layout
      const RU_TO_EN_MAP: Record<string, string> = {
        'и': 'b',
        'ч': 'x',
        // ... other key mappings
      };
      
      function normalizeKey(inputKey: string): string {
        return RU_TO_EN_MAP[inputKey.toLowerCase()] || inputKey;
      }
4. opencode-agent

   closed this as not plannedon Oct 17, 2026
5. opencode-agent commented on Oct 17, 2026

   

   opencode-agentBot

   on Oct 17, 2026 – with OpenCode Agent

   Contributor

   More actions

   We're closing this issue for now because we haven't heard back about which terminal you run OpenCode in (Windows Terminal and its version, conhost, WezTerm, VS Code, etc.).

   We need that to reproduce the problem. OpenCode v2 can only match shortcuts by physical key on a Russian layout if the terminal reports the base-layout key, so without knowing the terminal we can't tell an OpenCode bug from a terminal limitation.

   If this still happens on the latest v2, please reopen this issue or open a new one with your terminal and its version, and say whether other letter shortcuts (e.g. Ctrl+C) work with the Russian layout. Thanks for reporting!