gemini-cli - 💡(How to fix) Fix bullshit [2 comments, 2 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#25539Fetched 2026-04-17 08:55:29
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×2
RAW_BUFFERClick to expand / collapse

What happened?

bug-report-history-1776355617329.json

[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.

What did you expect to happen?

your model is frustrating one day it works excellent the next day it is absolutely for the trashcan! It is unacceptable to deceive a user in this way!

Client information

  • CLI Version: 0.38.1
  • Git Commit: 7f5580034
  • Session ID: 87716e51-28b4-42e5-8e58-bb6466bf815f
  • Operating System: linux v22.22.2
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3-flash-preview
  • Auth Type: oauth-personal
  • Memory Usage: 658.3 MB
  • Terminal Name: VTE(7600)
  • Terminal Background: #000000
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue may be related to the model's inconsistent performance, and attaching the exported chat history JSON file could help diagnose the problem.

Guidance

  • The user is experiencing inconsistent model performance, with the model working well one day and poorly the next, suggesting a potential issue with the model's training data or environment.
  • The user is asked to attach the exported chat history JSON file to help diagnose the issue, which could provide valuable information about the model's behavior.
  • The provided client information, such as the CLI version, Git commit, and model version, may be relevant to the issue and could be used to investigate further.
  • The user's operating system and terminal environment may also be a factor, and checking for any updates or configuration issues could be helpful.

Notes

The issue lacks specific technical details, and the cause of the problem is unclear. The guidance provided is based on the limited information available and may not be comprehensive.

Recommendation

Apply workaround: The user should attach the exported chat history JSON file to the issue to help diagnose the problem, as this may provide valuable information about the model's behavior.

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

gemini-cli - 💡(How to fix) Fix bullshit [2 comments, 2 participants]