Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix Gemini Reasoning Issues — Based on 3.1 Pro [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#26419•Fetched 2026-05-05 06:03:58
View on GitHub
Comments
2
Participants
3
Timeline
3
Reactions
0
Author
heartk0108heartk0108
Participants
gemini-cli[bot]gemini-cli[bot]heartk0108heartk0108sm1lysm1ly
Timeline (top)
commented ×2labeled ×1

Code Example

> /about
# paste output here
RAW_BUFFERClick to expand / collapse

What happened?

The reasoning servers are always unstable. Occasionally when the reasoning feels fast, it turns out to be a fake model — it shows "3.1 Pro" on the label, but it's actually using a model with inferior math and coding capabilities. Truly impressive. They have no intention of fixing bugs, only making users suffer. I wonder when it will ever get better.

Honestly, I like Google Gemini. I want to use it again — I've been lurking on GitHub, checking every now and then, wondering if there's ever a day without issues. I do plan to come back once things improve, but there are still ongoing bugs and service problems, so I'm not using it right now. I already got a refund previously. Currently using Codex, and if there are improvements, I will return to Gemini. Before advertising model performance and capabilities, please prioritize service quality and customer satisfaction first. I have no trust in it right now.

I used the Ultra plan for 2 months previously. The development team is also a problem. Instead of giving proper feedback and addressing the issues directly, whenever reasoning problems occur, they say things like "use a lower model" or "use an API key." Is it even appropriate for you to say that?

What did you expect to happen?

The reasoning servers are always unstable. Occasionally when the reasoning feels fast, it turns out to be a fake model — it shows "3.1 Pro" on the label, but it's actually using a model with inferior math and coding capabilities. Truly impressive. They have no intention of fixing bugs, only making users suffer. I wonder when it will ever get better.

Honestly, I like Google Gemini. I want to use it again — I've been lurking on GitHub, checking every now and then, wondering if there's ever a day without issues. I do plan to come back once things improve, but there are still ongoing bugs and service problems, so I'm not using it right now. I already got a refund previously. Currently using Codex, and if there are improvements, I will return to Gemini. Before advertising model performance and capabilities, please prioritize service quality and customer satisfaction first. I have no trust in it right now.

I used the Ultra plan for 2 months previously. The development team is also a problem. Instead of giving proper feedback and addressing the issues directly, whenever reasoning problems occur, they say things like "use a lower model" or "use an API key." Is it even appropriate for you to say that?

Client information

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

Run gemini to enter the interactive CLI, then run the /about command.

> /about
# paste output here
</details>

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue seems to be related to the instability and inaccuracy of the reasoning servers in Google Gemini, which may be mitigated by closely monitoring the service for updates and improvements.

Guidance

  • The user has already switched to an alternative service (Codex) due to ongoing issues with Gemini, suggesting that waiting for improvements might be a viable workaround.
  • To verify if the service has improved, the user can periodically check the Gemini GitHub page for updates on bug fixes and service quality enhancements.
  • The development team's response to issues, such as suggesting the use of a lower model or an API key, may indicate a need for more direct communication about the root causes of problems and plans for resolution.
  • Users experiencing similar issues might consider providing detailed feedback directly to the development team, including the output of the /about command from the Gemini CLI, to help identify and address specific problems.

Notes

The provided information does not specify a clear technical cause for the instability or a direct path to resolution, suggesting that the issue may be more related to service quality and customer support rather than a specific code or configuration problem.

Recommendation

Apply workaround: Given the lack of specific technical details and the mention of ongoing service issues, the best course of action seems to be waiting for the service to improve or exploring alternative solutions like Codex, as the user has already done.

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…
#api#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

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

Back to top recommendations

TRENDING