Bug: CLI crashes with --verbose flag on long prompts

[LUNCInsights]

The CLI crashes immediately when using --verbose with prompts over 500 chars.

Steps to reproduce:

1. npm install -g @google/gemini-cli
2. gemini --verbose "$(python3 -c 'print("A"*600)')"

Expected: verbose output
Actual: crash with exit code 1

---

[gemini-cli]

Although --verbose is not a recognized flag, the reported crash on long prompts suggests a potential issue in argument parsing or the relaunch mechanism when handling large inputs. Debugging this requires investigating the interaction between yargs and the child process spawning logic.

This issue describes a crash when using the --verbose flag with large inputs. Please provide your CLI version and verify if this issue persists in the latest release.

Effort Analysis:
The CLI architecture involves a lightweight parent process (packages/cli/index.ts) that spawns a heavy child process via node:child_process.spawn, passing arguments through getScriptArgs and getSpawnConfig in packages/cli/src/utils/processUtils.ts. While yargs is configured with .strict() in packages/cli/src/config/config.ts (which should normally print 'Unknown argument'), the report of a 'crash' specifically on prompts over 500 characters points to a possible buffer issue or an uncaught exception during the relaunch phase or within the ConsolePatcher (in packages/cli/src/ui/utils/ConsolePatcher.ts) which intercepts all console output. There is a known 500-character threshold in packages/core/src/services/sessionSummaryService.ts and packages/cli/src/ui/components/InputPrompt.test.tsx that may be relevant to how long strings are processed. Categorizing as medium due to the architectural complexity of cross-process argument passing and potential edge cases in yargs strict mode when combined with long positional arguments.