Repeated http requests

[Datamance]

I'm on a mac M1 with the latest version of crush installed (0.7.4). Charm is doing some dangerous churn which makes it completely unusable.

From the charm logs:

2025/09/05 20:33:27 DEBU HTTP Request body="{\"contents\":[{\"parts\":[{\"text\":\"Generate a concise title for the following content:\n\nFor some reason, it appears that the \\"custom-openai\\" configuration in my crush.json is resulting in the \\"GPT-5\\" option appearing _twice_ under the \\"custom-openai\\" provider in the TUI for crush. Why would this be happening? Please do some research with deepwiki and press on until you find out exactly what the issue is, at the code level.\"}],\"role\":\"user\"}],\"generationConfig\":{\"maxOutputTokens\":40},\"systemInstruction\":{\"parts\":[{\"text\":\"you will generate a short title based on the first message a user begins a conversation with\n\n- ensure it is not more than 50 characters long\n- the title should be a summary of the user's message\n- it should be one line long\n- do not use quotes or colons\n- the entire text you return will be used as the title\n- never return anything that is more than one sentence (one line) long\n\"}],\"role\":\"user\"},\"tools\":[{}]}" method=POST source=/home/runner/work/crush/crush/internal/log/http.go:46 url="map[ForceQuery:false Fragment: Host:generativelanguage.googleapis.com OmitHost:false Opaque: Path:/v1beta/models/gemini-2.5-flash:streamGenerateContent RawFragment: RawPath: RawQuery:alt=sse Scheme:https User:<nil>]"
2025/09/05 20:33:29 DEBU HTTP Response body="" content_length=0 duration_ms=1982 error=<nil> headers="map[Alt-Svc:[h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000] Content-Disposition:[attachment] Content-Length:[0] Content-Type:[text/event-stream] Date:[Sat, 06 Sep 2025 00:33:29 GMT] Server:[scaffolding on HTTPServer2] Server-Timing:[gfet4t7; dur=1958] Vary:[Origin X-Origin Referer] X-Content-Type-Options:[nosniff] X-Frame-Options:[SAMEORIGIN] X-Xss-Protection:[0]]" source=/home/runner/work/crush/crush/internal/log/http.go:68 status="200 OK" status_code=200
2025/09/05 20:33:29 DEBU HTTP Request body="{\"contents\":[{\"parts\":[{\"text\":\"Generate a concise title for the following content:\n\nFor some reason, it appears that the \\"custom-openai\\" configuration in my crush.json is resulting in the \\"GPT-5\\" option appearing _twice_ under the \\"custom-openai\\" provider in the TUI for crush. Why would this be happening? Please do some research with deepwiki and press on until you find out exactly what the issue is, at the code level.\"}],\"role\":\"user\"}],\"generationConfig\":{\"maxOutputTokens\":40},\"systemInstruction\":{\"parts\":[{\"text\":\"you will generate a short title based on the first message a user begins a conversation with\n\n- ensure it is not more than 50 characters long\n- the title should be a summary of the user's message\n- it should be one line long\n- do not use quotes or colons\n- the entire text you return will be used as the title\n- never return anything that is more than one sentence (one line) long\n\"}],\"role\":\"user\"},\"tools\":[{}]}" method=POST source=/home/runner/work/crush/crush/internal/log/http.go:46 url="map[ForceQuery:false Fragment: Host:generativelanguage.googleapis.com OmitHost:false Opaque: Path:/v1beta/models/gemini-2.5-flash:streamGenerateContent RawFragment: RawPath: RawQuery:alt=sse Scheme:https User:<nil>]"
2025/09/05 20:33:29 DEBU HTTP Response body="" content_length=0 duration_ms=564 error=<nil> headers="map[Alt-Svc:[h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000] Content-Disposition:[attachment] Content-Length:[0] Content-Type:[text/event-stream] Date:[Sat, 06 Sep 2025 00:33:30 GMT] Server:[scaffolding on HTTPServer2] Server-Timing:[gfet4t7; dur=545] Vary:[Origin X-Origin Referer] X-Content-Type-Options:[nosniff] X-Frame-Options:[SAMEORIGIN] X-Xss-Protection:[0]]" source=/home/runner/work/crush/crush/internal/log/http.go:68 status="200 OK" status_code=200

That loop of request and response to the google gemini API happens over and over and over again, which actually significantly spiked my cloud costs while charm decided to run amok for several minutes - I didn't even know it was happening until I tailed the logs. No idea why the response content is empty, but the debounce logic here is downright hostile considering you're asking users to supply their own API keys.

[meowgorithm]

Oof. Thank for the detailed report and the detailed logs. I'm very sorry about the cost spike.

From what I can tell, Crush is trying to autogenerate a title, Gemini is returning 200 OK, but with an empty response, and Crush is on retrying with no backoff (@kujtimiihoxha, please correct me if I'm wrong here). If I'm correct, we absolutely need guardrails in place for situations like this.

We take this kind of thing seriously and keep this issue updated with status.

One quick thing to clarify: were you using Gemini via Google directly, or through OpenRouter?

[kujtimiihoxha]

@Datamance I am really sorry this happened, it turns out that there where a couple issues in the current implementation.

• We try to set the maxOutputTokens for the provider to a low value so that we make sure the model does not generate super log titles.
• For some reason with the gemini provider this results in the model returning no content.
• The provider loop did not handle the case of no content as expected and looped forever.
• We did not use the main loop context so when you cancel the request or the main agent is done the loop was continuing.

I fixed the loop issue and added special handling for the gemini provider so that the max token output is bigger for gemini models.

Again really sorry this happened and thanks for submitting the issue.

[meowgorithm]

Just a note that this is fixed as of the newly-released v0.7.6.

@Datamance, thanks again for filing the issue. If, by chance, the issue isn't fixed please re-open and we'll address.

[Datamance]

One quick thing to clarify: were you using Gemini via Google directly, or through OpenRouter?

Was using Gemini via Google.

Thank you guys for the quick response. I will try to give it another spin over the next few days.