gemini-cli - 💡(How to fix) Fix Stats show no quota info [1 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#25393Fetched 2026-04-15 06:45:04
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
1
Author
Participants
Timeline (top)
labeled ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

What happened?

No matter how long I work with CLI, every time I run /stats session or /stats model I see nothing - just like I had a clean session state. However, the footer does show the quota info.

What did you expect to happen?

As before this regression, I expect to see the quota info related to the session and model, as well as the remaining general quota and when it resets.

Client information

  • CLI Version: 0.39.0-nightly.20260414.gdaf500623
  • Git Commit: 5781aa6f0
  • Session ID: a72460f1-f743-4aaf-b567-149fd7a29c22
  • Operating System: win32 v24.14.0
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3.1-pro-preview
  • Auth Type: oauth-personal
  • Memory Usage: 416.4 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue might be related to the CLI version or session state, and checking the session state or trying a different CLI version could help resolve the issue.

Guidance

  • Verify that the session state is being properly updated by checking the session ID and ensuring that it matches the expected session.
  • Check the CLI version and consider trying a different version, such as a stable release, to see if the issue persists.
  • Review the quota info in the footer to ensure that it is accurate and up-to-date.
  • Consider providing more information about the session and model being used to help troubleshoot the issue.

Notes

The issue may be specific to the nightly build of the CLI or the gemini-3.1-pro-preview model version, and more information about the session and model may be needed to fully resolve the issue.

Recommendation

Apply workaround: Try a different CLI version, such as a stable release, to see if the issue persists, as the nightly build may be causing the problem.

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