[Bug] In PowerShell, the mouse scroll wheel scrolls command history instead of the CLI's output

[YCX81]

What happened?

After updating gemini-cli to the latest version (0.15.0), I've encountered an interactive usability issue when using it in Windows PowerShell: when I try to use my mouse scroll wheel to scroll up and review the response that was just generated, the terminal's output buffer does not scroll. Instead, my PowerShell input prompt begins cycling through my previous command history.

What did you expect to happen?

Using the mouse scroll wheel should scroll the PowerShell window's output buffer, allowing me to easily read the full response from gemini-cli

Client information

Client Information

Run gemini to enter the interactive CLI, then run the /about command.

> /about
# paste output here

About Gemini CLI │
│ │
│ CLI Version 0.15.0 │
│ Git Commit 37af6f4 │
│ Model auto │
│ Sandbox no sandbox │
│ OS win32 │
│ Auth Method OAuth │
│ IDE Client VS Code

Login information

Google Account

Anything else we need to know?

No response

[gemini-cli]

Found possible duplicate issues:

• Duplicated text while scrolling (in Powershell) #12865
• CLI UI issue while scrolling up #7282

If you believe this is not a duplicate, please remove the status/possible-duplicate label.

[iSanto]

Install latest version of node.js 25+

[israelgonzalezb]

Updated to Node 25 but gemini-cli was broken in a new way in Powershell. Switched to nushell and it runs perfectly again.

[djoleluk]

I have the same issue with the vertical scrolling, the latest 0.15.0 and 0.15.1 updates broke it. U use nvim, zsh shell, and hyprland on Ubuntu 25.10 on Wayland. Reverting to the Gemini CLI 0.14.0 version fixed the issue for now. And I had to disable annoying automatic update attempts by Gemini Cli in the settings.json file for now, because i can't update and use the latest version with this bug in place. This should be addressed asap for the new version, so i can track this issue and update the CLI manually when it's resolved, and maybe enable auto updates again. It's a very important feature. Also, auto updates do not use sudo, so they fail anyway for users that have sudo privileges implemented on their Linux systems, and i have to run the update command myself. This feature can also be improved in some future versions of Gemini CLI, either by introducing sudo to the npm install -g @google/gemini-cli or by just implementing an auto reminder to the user to do the update manually, instead of these constant failure attempts. I think the latter is a better way.