gemini-cli - 💡(How to fix) Fix "Model stream ended with empty response text." [1 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#25582Fetched 2026-04-18 05:57:44
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

What happened?

bug-report-history-1776437737181.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?

Create a .md file with a list of filenames and image descriptions and dates

Client information

  • CLI Version: 0.38.1
  • Git Commit: 7f5580034
  • Session ID: 370541d0-6b6c-4487-af61-3aad173a18dd
  • Operating System: win32 v24.14.1
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: gemini-api-key
  • Memory Usage: 780.0 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

bug-report-history-1776437737181.json

extent analysis

TL;DR

The issue can likely be resolved by examining the exported chat history JSON file for errors or inconsistencies that prevented the creation of the expected .md file.

Guidance

  • Review the contents of the bug-report-history-1776437737181.json file to identify any potential issues or errors that may have caused the failure to create the .md file.
  • Check the file for any missing or malformed data that could be preventing the successful creation of the list of filenames, image descriptions, and dates.
  • Verify that the CLI version (0.38.1) and model version (auto-gemini-3) are compatible and up-to-date.
  • Consider sharing the exported chat history JSON file to facilitate further investigation and troubleshooting.

Notes

The provided information is limited, and without access to the JSON file or more detailed error messages, it's challenging to provide a more specific solution. The guidance provided is based on the assumption that the issue is related to the data or compatibility.

Recommendation

Apply workaround: Share the exported chat history JSON file to facilitate further investigation and troubleshooting, as this may help identify the root cause of the issue and lead to a more specific solution.

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 "Model stream ended with empty response text." [1 comments, 2 participants]