Repository navigation
Enter key and inputs not registering in interactive menus (WSL) #329
Description
Expected Behavior
When navigating Command Code interactive menus, pressing the "Enter" key or providing standard inputs should register the selection and proceed to the next step. Ctrl + C should immediately terminate the process.
Actual Behavior
Inputs do not register at all across any of the interactive menus, leaving the user completely stuck. Specifically, the "Enter" key does not work, though Shift + Tab does register. Additionally, attempting to abort the process using Ctrl + C is unresponsive and requires the user to "spam" the keystroke before it eventually listens. This issue is persistent and happens 100% of the time, completely blocking usage of the menus.
Command Code Version
0.25.5
Operating System
Windows
Terminal/IDE
VS Code integrated terminal, Windows Terminal, Tmux
Shell
Zsh, Bash
Additional context
This issue was discussed in the Discord channel. It was noted that this happens continuously ("all the time") and prevents getting past any of the menus. It happens across different terminals and shells within the WSL environment.
I've uploaded a video here:
https://discord.com/channels/1255220079029653626/1501338502003163338/1501663962117312583
Activity
naymurdev commentedon May 6, 2026
Hello @Copystrike , sorry to hear you're still facing this issue.
I’m also on Windows, but I don’t run everything through Windows terminals directly. I mainly use
Ubuntu/WSLterminal, and it’s been working fine for me without these kinds of issues.From what you mentioned, you’re using VS Code, Windows Terminal, zsh, bash, and tmux and the issue might be coming from how tmux or the terminal layer is interacting with WSL.
What works for me is a much simpler flow:
code .When VS Code opens this way, you’ll see
WSL: Ubuntuin the bottom-left corner. That’s important because it means VS Code is running inside Linux (WSL), not native Windows. This avoids a lot of path, shell, and environment issuesvipulgupta2048 commentedon May 18, 2026
Please confirm if you are still facing this issue? Closing this one out till then. Feel free to comment/open it again.
Copystrike commentedon May 18, 2026
@vipulgupta2048 Its still happening, only progression now is that I can use my arrow keys and use the esc button once to stop it but still I cannot press enter or a number.
I cannot reopen this issue.
saqibameen commentedon May 19, 2026
@asharirfan @arre-ankit was this issue resolved on windows?
asharirfan commentedon May 19, 2026
@Copystrike I just tested Command Code in WSL with both Git bash and Windows Terminal. The enter key is working as expected. Even the numbers are working correctly.
Can you please let us know anything else about your setup that can help us debug this issue?
naymurdev commentedon Jun 4, 2026
@Copystrike Sorry you're still facing this issue. @asharirfan and I both tested it on WSL using VS Code terminal, the native WSL terminal, and even PowerShell with WSL.
So my main question is: Are you actually using WSL, or are you just using PowerShell? I saw in the title that you mentioned WSL, but since it's working fine for both of us, I just want to understand your exact setup and what version you're on.
Here's my WSL version for reference:
WSL version: 2.7.3.0
Kernel version: 6.6.114.1-1
WSLg version: 1.0.73
MSRDC version: 1.2.6676
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.19045.6466
lehuuphuc commentedon Jun 11, 2026
I am using MacOS 26.5.1
I have the same issue: cannot use arrow up/down or enter key to confirm a selection (arrow left/right still works).
Suggestion: While the bug is under investigation, consider defining shortcuts for each selection item (e.g., "cmd + 1" for option #1).
naymurdev commentedon Jun 11, 2026
Yes, we're working on this issue and will ship the fix very soon
Thanks for reporting
asharirfan commentedon Jun 11, 2026
@lehuuphuc Which terminal are you using? Also, which version of Command Code are you using?
lehuuphuc commentedon Jun 12, 2026
@asharirfan
I am using the latest version (v0.35.0) on the MacOS default terminal, but I also experience the same issue with Warp and the VSCode terminal.
I just started using CommandCode yesterday, and it appears to be a critical blocker for me.
asharirfan commentedon Jun 12, 2026
@lehuuphuc Warp as in the VPN service?
lehuuphuc commentedon Jun 13, 2026
@asharirfan
I meant Warp terminal at warp.dev
vipulgupta2048 commentedon Aug 4, 2026
Thanks for letting us know, working on this. cc: @naymurdev
Just a quick check, is this still a issue on latest v1 of Command Code?
naymurdev commentedon Aug 6, 2026
I just checked it again and I didn’t face the issue in Warp terminal or other terminals either. So @lehuuphuc , can you confirm that you guys are still facing this issue in v1? v1 is the most capable version of CommandCode, so try it and let us know
naymurdev commentedon Aug 14, 2026
Closing this PR. If you still face the issue, please reopen it.