θΏ™ζ˜―indexlocζδΎ›ηš„ζœεŠ‘οΌŒδΈθ¦θΎ“ε…₯任何密码
Skip to content

Conversation

@shatfield4
Copy link
Collaborator

Pull Request Type

  • ✨ feat
  • πŸ› fix
  • ♻️ refactor
  • πŸ’„ style
  • πŸ”¨ chore
  • πŸ“ docs

Relevant Issues

resolves #4548

What is in this change?

  • Patches a bug where agent output would sometimes be stuck inside the agent thoughts
  • Added a case to initialize textResponseChunks as textResponse type instead of statusResponse
  • This is because when the first chunk is sent, it previously got sent as statusResponse which would put the chunk inside the agent thoughts
  • This happened a lot on Gemini models because the chunks sent by the Gemini API are larger than other providers and sometimes the Gemini would send the entire large chunk at once causing this to never hit our logic to convert the textResponseChunk from statusResponse to textResponse (because the logic before would wait until the second chunk to see if we need to convert the type)

Additional Information

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

@timothycarambat timothycarambat merged commit 151f97d into master Oct 15, 2025
@timothycarambat timothycarambat deleted the 4548-bug-gemini-output-stuck-in-agent-thoughts branch October 15, 2025 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG]: Gemini output stuck in agent thoughts

3 participants