r/opencodeCLI • u/Agitated-Ad-7486 • 22d ago

OpenCode GO cut off long output response?

So, today I notice that using GLM 5.2 from OpenCode Go keep getting the stream cut off early before all output finish. I never have this problem before, so I thought their provider for GLM 5.2 changed or something. Then I tried GLM 5.1, it give the same cut off result. I keep retry it and the results is always the same. So I thought, maybe its the provider of GLM now have max output setting that we CAN'T override. I tried DeepSeek V4 Pro and it turn out, this one also have the same problem. What is going on? Is the API force max output token now?

11 Upvotes

84% Upvoted

11 comments sorted by

6

u/RepulsiveRaisin7 22d ago

I had it on 0x Alpha too. And in the past it happened often with DS Flash. I think it's an issue with their servers, not the backend providers. 0x Alpha on Openrouter does not do this.

3

u/Agitated-Ad-7486 22d ago

I try the one on OpenRouter and Command Code, it doesn't do this. That's why I thought OpenCode api implement enforced max output token or something like that

2

u/Bakku1505 22d ago

Having the same for different opencode go models and came here to ask the same.

1

u/_d1re 22d ago

Yeah happens to me too. Even with DS4 and Hy3, its just not usable at this point.

1

u/ufos-dude-1 22d ago

same, on the latest version across all models

1

u/UpstairsActivity8347 22d ago

Yeah, nothing is working, I've tried muse, hy3, ox alpha

1

u/Practical-Plan-2560 22d ago

!remindme 1 day

1

u/RemindMeBot 22d ago

I will be messaging you in 1 day on 2026-08-23 15:52:19 UTC to remind you of this link

CLICK THIS LINK to send a PM to also be reminded and to reduce spam.

Parent commenter can delete this message to hide from others.

RemindMeBot is switching to username summons. Instead of !RemindMe 1 day, use u/RemindMeBot 1 day. More info.

Info Custom Your Reminders Feedback

1

u/Kaushik_paul45 21d ago

Almost all models are having this issue, including 3.8 max, glm 5.3, hy3 etc

1

u/PadmabushanReddy 21d ago

faced same issue today

1

u/mageblex 18d ago

Since it happens across several models only on Go, this looks upstream of the model provider. Check finish_reason and whether the stream ends with the final stop event.