git status: cleanBuild history for GGUF files
See what changed
in your GGUF.
ModelBake remembers the model, converter, settings, and files from your last build. Build again and it shows the difference.
- runs locally
- never uploads your model
- free and open source
- macOS + Linux
python -m pip install https://modelbake.dev/downloads/modelbake_ai-0.1.0-py3-none-any.whlmodelbake tourFREE FOREVER · APACHE-2.0 · NO ACCOUNT
Easy to review.
no changenew converternew GGUF bytesWhy Git is not enough
Git says clean.
The release changed.
Your code can stay the same while the downloaded model, converter, or finished GGUF changes. ModelBake checks all of them.
sha256 movedsha256 movedThe actual product
Every build gets one readable record. The next build gets a clear before-and-after.
Remember.
Then compare.
No model required
Try a sample build.
Replay a tiny example and open any step. Nothing is uploaded and no real model is needed.
loading…fixture/v0modelbake.fixture/v0this fixture runnerWhy you come back
Every new build
gets easier.
Unchanged work is reused. Changed work is obvious.
62f84e2a…ac8717d1…$ modelbake compare approved/manifest.json candidate/manifest.json
recipe: changed recorded source digest: same
declared runner: same observed runner: same
↺ source reused_from_cache recorded digest same
↺ convert-f16-base reused_from_cache recorded digest same
↺ quantize-q4 reused_from_cache recorded digest same
↺ smoke-q4 reused_from_cache recorded digest same
+ quantize-q8 added recorded output added
+ smoke-q8 added fixture observation added
No promotion decision inferred.
Add it to your current workflow
Keep Git.
Add one check.
ModelBake runs beside Git and llama.cpp. Add one CI step and every GGUF release gets a record and a comparison.
- uses: ./.github/actions/modelbake
with:
recipe: modelbake.yaml
baseline-store: .modelbake/baselines
baseline-name: production
enable-github-cache: "false"
upload-evidence: "false"
✓ record the artifact bytes produced
✓ verify the current bytes
✓ compare with the accepted predecessor
✓ stop local acceptance when bytes move
SOURCE + CI EXAMPLE INCLUDED ↓
Evidence, correctly named
Know what
green means.
Output bytes were produced and digested.
No model quality conclusion.
The fixture adapter decoded each requested test artifact.
That any model runtime opened them.
The manifest records source, recipe, runner, and output digests.
Future reproduction, license, security, or production readiness.
“A green process exit is not a green model.”
Local from the first build
Run the
first diff.
The local CLI stays free. No account. No model upload. One command shows the complete baseline → candidate → diff loop.
01 python -m pip install https://modelbake.dev/downloads/modelbake_ai-0.1.0-py3-none-any.whl
02 modelbake tour
baseline → candidate → exact release diff