gemini-cli - 💡(How to fix) Fix [Regression][Accessibility] /stats command output is gutted in v0.38.0 – Information missing, not just formatted [5 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#25441Fetched 2026-04-16 07:06:27
View on GitHub
Comments
5
Participants
3
Timeline
7
Reactions
3
Timeline (top)
commented ×5labeled ×2
RAW_BUFFERClick to expand / collapse

What happened?

Following the fix for Issue #23369 in version 0.38.0, the /stats command has become practically useless for users relying on screen readers and Braille displays. While it's true that the graphical "noise" (the block characters) has been removed, the actual data—specifically the quota usage and model stats—has vanished along with it. Steps to Reproduce: 1. Enable accessibility.screenReader: true in settings.json. 2. Run /stats. 3. Observe the output. User: /stats
Session Stats
Interaction Summary
Session ID: eb2c6f04-f5f2-4b5e-b1e8-3bcd93376d80
Auth Method: Signed in with Google ([email protected])
Tier: Gemini Code Assist in Google One AI Pro
Tool Calls: 0 ( ✓ 0 x 0 )
Success Rate: 0.0%
Performance
Wall Time: 13.4s
Agent Active: 0s
» API Time: 0s (0.0%)
» Tool Time: 0s (0.0%)
/model
gemini-3-flash-preview context
0% used
Shift+Tab to accept edits

Actual Behavior: The output is stripped of all meaningful data. It shows "0% used" regardless of actual usage or simply omits the relevant lines. The UI fix effectively broke the feature's core functionality. Questions for the Dev Team: 1. What kind of QA process was performed before merging PR #23442 into a stable release? Was it actually tested with a screen reader, or did someone just assume that "less text equals more accessibility"? 2. In what world is "removing the data" considered a valid solution for an accessibility bug? Accessibility means making information reachable, not deleting it to avoid formatting challenges. This is a disaster for blind users who rely on these metrics to manage their sessions. We expected a professional fix, not a lobotomized command. Please address this regression immediately. Environment: • Version: 0.35.3 -> 0.38.0 • OS: Windows (NVDA / Braille Display) • Terminal: Windows Terminal / CMD

What did you expect to happen?

The command should return the usage data in a clear, text-only format (e.g., "Usage: 45%"), reset in [hh:mm] at [hh:mm].

Client information

  • CLI Version: 0.38.0
  • Git Commit: 3f0873a83
  • Session ID: 60e3728d-a824-46f7-b7df-49418ba70907
  • Operating System: win32 v25.9.0
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3-flash-preview
  • Auth Type: oauth-personal
  • Memory Usage: 273.2 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Login information

Auth web Google account.

Anything else we need to know?

No response

extent analysis

TL;DR

The /stats command likely needs to be updated to include the quota usage and model stats in a text-only format for screen reader compatibility.

Guidance

  • Review the changes made in PR #23442 to identify why the data was removed and consider reverting or modifying those changes to include the necessary information.
  • Test the /stats command with a screen reader to ensure that the output is accessible and includes the required data.
  • Consider adding a configuration option to allow users to choose between a graphical and text-only output for the /stats command.
  • Verify that the issue is specific to version 0.38.0 and does not occur in previous versions, such as 0.35.3.

Notes

The issue seems to be related to the changes made in version 0.38.0, specifically PR #23442, which removed the graphical "noise" but also removed the necessary data. The fix should focus on restoring the data in a text-only format.

Recommendation

Apply a workaround by reverting the changes made in PR #23442 or modifying them to include the necessary data in a text-only format, as the current implementation breaks the core functionality of the /stats command for screen reader users.

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