Repository navigation
Modernize browser demo models with supported NanoGPT choices - #4
Merged
Merged
Conversation
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
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.
The browser demos used factory model IDs that are no longer advertised in NanoGPT's current catalog. Use
xiaomi/mimo-v2.6-flashfor diff generation and scoped repairs, and pin MiMo 2.6 Pro and GLM 5.3 Flash as inexpensive alternatives. Existing factory selections migrate; custom saved choices remain intact.The decision demo keeps MiMo 2.6 Flash and requests its supported
nonereasoning effort. Preserve catalog creation dates so the picker can rank each lab's newer flagship correctly. Public catalog excerpts record the IDs, capabilities, and prices verified on 2026-10-13.Validation:
This changes demo pages, documentation, and tests. Library defaults, package versions, release checks, and UTF-8/binary handling are unchanged. The existing CI release-test failure is reproducible in a shallow checkout without tags: package 0.3.0 has no unreleased entry when no release tags are visible. This PR deliberately does not include that separate release fix.