bug1

### What happened?

Cli is not working

### What did you expect to happen?

cli is not working

### Client information

* **CLI Version:** 0.50.0
* **Git Commit:** 8d9733d53
* **Session ID:** 583b02ce-7ff4-44fa-bdbf-0362bd6042ef
* **Operating System:** win32 v24.18.0
* **Sandbox Environment:** no sandbox
* **Model Version:** gemini-3.1-pro-preview-customtools
* **Auth Type:** gemini-api-key
* **Memory Usage:** 257.0 MB
* **Terminal Name:** xterm.js(6.1.0-beta.288)
* **Terminal Background:** #191a1b
* **Kitty Keyboard Protocol:** Supported

### Login information

_No response_

### Anything else we need to know?

_No response_

No source file, test, command, or reproduction steps are identified. Start by reproducing the CLI failure with version 0.50.0 on win32 using the provided environment details, then trace the failing entry point; the work is done when the specific failure is identified, fixed, and covered by a regression check.

Written by the indexing model from the issue text.