feat(models): add Gemma 4 QAT local models - #1268
Merged
Merged
Conversation
This was referenced Jul 21, 2026
gabrielste1n
approved these changes
Jul 22, 2026
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.
Summary
Google published official QAT builds of the Gemma 4 GGUFs, smaller than the bartowski Q4_K_M quants we ship and closer in quality to the unquantized weights. This adds them as four new local registry entries (31B, 26B MoE, E4B, E2B) pointing at the ungated
google/gemma-4-*-qat-q4_0-ggufrepos, which the app's plain unauthenticated downloader can fetch. Repo ids, filenames and byte sizes come straight from the HuggingFace tree API, since the upstream filename shape (gemma-4-31B_q4_0-it.gguf) does not follow the bartowski naming.The existing q4_k_m entries are untouched, so nobody's downloaded model gets orphaned or force re-downloaded. The QAT builds are a separate opt-in download. The only edit to an existing entry is moving the "Recommended" badge from E4B Q4_K_M to the E4B QAT entry (the flag only renders a badge in the picker, nothing selects a model by it). One caveat: llama.cpp has an open report (ggml-org/llama.cpp#24311) of garbage output with Gemma 4 QAT on Vulkan with GPU offload, seen with unsloth's UD quants rather than these official q4_0 files. The default CPU path and Metal are unaffected.
Fixes #918
Changes