gemini-cli - 💡(How to fix) Fix Global state leakage in terminalCapabilityManager singleton [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#26808Fetched 2026-05-11 03:27:49
View on GitHub
Comments
2
Participants
3
Timeline
13
Reactions
0
Timeline (top)
labeled ×6commented ×2added_to_project_v2 ×1closed ×1
RAW_BUFFERClick to expand / collapse

What happened?

terminalCapabilityManager maintains global singleton state that is mutated by multiple components. This leads to state leakage between tests and unpredictable behavior in complex CLI flows.

What did you expect to happen?

Use a context-based manager or provide a robust reset mechanism for testing.

Client Information

<details> <summary>Client Information</summary>

OS: linux Date: Sunday, May 10, 2026 Gemini CLI: 0.42.0-nightly

</details>

Login information

Automated audit with Gemini CLI.

Anything else we need to know?

File: packages/cli/src/ui/utils/terminalCapabilityManager.ts. Primarily impacts test reliability and multi-instance scenarios.

Severity: Low Area: area/core

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING