google-gemini/gemini-cli

[Windows/WezTerm] Shift+Tab and fallback F10 fail to cycle approval mode (Keystroke logs included)

Open

#22738 opened on Mar 16, 2026

View on GitHub
 (3 comments) (0 reactions) (1 assignee)TypeScript (103,992 stars) (13,657 forks)batch import
area/platformeffort/smallhelp wantedkind/bugpriority/p3status/bot-triagedstatus/need-information

Description

Describe the bug

On Windows 11 using WezTerm and PowerShell, pressing Shift+Tab fails to cycle the approval mode (e.g., to /plan). The fallback key F10 also does not work.

Other TUI tools (like Claude Code and Codex) handle Shift+Tab perfectly in the exact same WezTerm panes, indicating a specific sequence parsing issue in Gemini CLI for Windows ConPTY environments.

Environment

  • OS: Windows 11
  • Terminal: WezTerm (running PowerShell)
  • Node version: v22.12.0
  • Gemini CLI version: 33.1

Keystroke Logs (Pressing F12)

1. When pressing Shift+Tab: It seems ConPTY strips the escape sequence and passes it as a raw \t: ℹ [DEBUG] Raw StdIn: "\t" ℹ [DEBUG] Keystroke: {"name":"tab","shift":false,"alt":false,"ctrl":false,"cmd":false,"insertable":false,"sequence":"\t"}

2. When pressing F10 (Fallback key): The sequence \u001b[21~ sent by WezTerm does not trigger the CYCLE_APPROVAL_MODE action: ℹ [DEBUG] Raw StdIn: "\u001b[21~" ℹ [DEBUG] Keystroke: {"name":"f10","shift":false,"alt":false,"ctrl":false,"cmd":false,"insertable":false,"sequence":"\u001b[21~"}

Expected Behavior

Either Shift+Tab should correctly cycle the mode, or the F10 sequence \u001b[21~ should be mapped to the CYCLE_APPROVAL_MODE command for WezTerm users on Windows.

Contributor guide

Tech stack
typescriptnodejs
Domain
clideveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic Node.jsterminal emulator awareness
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The user reports that Shift+Tab sends a raw tab character instead of the shift+tab sequence in WezTerm. Investigate the CLI's key mapping logic in src/input/keymap.ts or similar. Look at how other TUI tools handle this and compare. For F10, check if the escape sequence \u001b[21~ is correctly mapped in the CLI's keybindings. The logs indicate both keys are received but not triggering the CYCLE APPROVAL MODE action. Consider adding a fallback mapping for WezTerm on Windows.