Repository navigation
fix(chat): switch to glm-5.3-flash as mimo-v2.5 is retired - #311
Merged
Merged
Conversation
mimo-v2.5 is no longer in the OpenCode Go model list, and mimo-v2.5-free on zen/v1 rejects server calls with FreeTierError (403). The router fails inconsistently for mimo-v2.5 (works from some edges, FreeTierError from Vercel egress). Switches to glm-5.3-flash, verified via direct API call including tool calling.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Switches the assistant's model from
mimo-v2.5/mimo-v2.5-freetoglm-5.3-flashonhttps://opencode.ai/zen/go/v1.Why
OpenCode removed
mimo-v2.5from the Go router's model list, andmimo-v2.5-freeonzen/v1rejects server-side calls withFreeTierError (403). The router fails inconsistently for the retired model (works from some egress IPs, fails from Vercel). Every chat request errored at stream start, surfacing as 'Something went wrong' in the widget.How to test
curl -X POST /api/chat -d '{"messages":[{"role":"user","parts":[{"type":"text","text":"Hi"}]}]}'— stream should containstart→ text deltas →finish, nottype:error.