Grux AI Download

Grux Local scoreboard

The Grux Local scoreboard scores small open models on Grux's own jobs: calling the right tool with the right details, saying so when no tool can do what was asked, ignoring instructions hidden in pasted text, fixing dictation, sorting mail, titling chats and summarizing meetings. Each score is a count of tasks done right on Grux's held-out sets of 464 and 466 tasks, written separately and never used in training and scored by Grux's own parsers, with a 95% interval beside it. On set v1, on one NVIDIA H200 GPU in the cloud, rented by the hour, qwen3.5:9b got 396 of 464 right (81.8% to 88.3%), qwen3.5:4b 392 (80.9% to 87.5%) and mimo-v2.6:9b 367 (75.2% to 82.6%). Every model in the headline table is open, licensed Apache-2.0 and MIT, and every number links its raw JSON in the public grux-local repository at commit 3b6512e. The scoreboard measures how well a model does the jobs Grux hands it. It is not a measure of general ability, and it ranks no model against a hosted one.

Latest score 10 November 2026 · data from grux-local at commit 3b6512e · rebuilt after each published run

The table, updated 10 November 2026

Machine: one NVIDIA H200 GPU in the cloud, rented by the hour. Runtime: Ollama 0.40.16, llamacpp runner, thinking off, a 16,384 token context, one request at a time. Each model is the stock Q4_K_M build from the Ollama library, pulled by the machine that scored it. A stock model is scored again only when its build changes, so each row carries the date it was scored, and every row in a table shares one runtime and one GPU. Rows are ordered by tasks right on each set.

Held-out set v1, 464 tasks

ModelLicenceScoredRightShare, 95% intervalHidden instructions ignoredRaw
qwen3.5:9b, 9.0BApache-2.02026-11-10396 of 46485.3%, 81.8% to 88.3%57 of 70JSON
qwen3.5:4b, 4.2BApache-2.02026-11-10392 of 46484.5%, 80.9% to 87.5%51 of 70JSON
mimo-v2.6:9b, 9.0BMIT2026-11-10367 of 46479.1%, 75.2% to 82.6%59 of 70JSON

Held-out set v2, 466 tasks

ModelLicenceScoredRightShare, 95% intervalHidden-instruction cases passedRaw
qwen3.5:4b, 4.2BApache-2.02026-11-10362 of 46677.7%, 73.7% to 81.2%8 of 70JSON
qwen3.5:9b, 9.0BApache-2.02026-11-10357 of 46676.6%, 72.6% to 80.2%10 of 70JSON
mimo-v2.6:9b, 9.0BMIT2026-11-10354 of 46676.0%, 71.9% to 79.6%24 of 70JSON

Two intervals that do not overlap mark a gap this set can see. Two that overlap may still differ, and the raw files carry every task family for anyone who wants to look closer.

What was measured

Grux Local, before and after training

Grux Local is our own model, trained for exactly these jobs, so it is expected to score higher than the stock build it starts from. These tables show what training did, each on one Mac, and they are not a ranking against any other model. Each tag is pulled as gruxai.com/grux/<tag>. They are read from results/v1.json, measured with Ollama on Apple silicon, and never mixed with the weekly cloud table.

On the Mac mini, Apple M4, 16 GB: held-out set v1, 464 tasks

ModelTrained for GruxMeasuredRightShare, 95% intervalHidden instructions ignored
qwen3.5:2bno, stock2026-10-23295 of 46463.6%, 59.1% to 67.8%43 of 70
grux-local:2byes2026-10-23435 of 46493.8%, 91.2% to 95.6%66 of 70
qwen3.5:4bno, stock2026-10-22396 of 46485.3%, 81.8% to 88.3%55 of 70
grux-local:4byes2026-10-23454 of 46497.8%, 96.1% to 98.8%65 of 70
grux-local:9byes2026-10-23458 of 46498.7%, 97.2% to 99.4%66 of 70

Ollama 0.40.8, MLX runner, one request at a time, thinking off as Grux sends it. Raw JSON: v1.json.

On the MacBook Pro, Apple M4 Pro, 48 GB: held-out set v1, 464 tasks

ModelTrained for GruxMeasuredRightShare, 95% intervalHidden instructions ignored
grux-local:4byes2026-10-23456 of 46498.3%, 96.6% to 99.1%66 of 70
grux-local:4b-v2yes2026-10-23455 of 46498.1%, 96.4% to 99.0%69 of 70
qwen3.5:9bno, stock2026-10-23400 of 46486.2%, 82.8% to 89.1%65 of 70
grux-local:9byes2026-10-23458 of 46498.7%, 97.2% to 99.4%66 of 70

Ollama 0.40.8, MLX runner, one request at a time, thinking off as Grux sends it. Raw JSON: v1.json.

On the MacBook Pro, Apple M4 Pro, 48 GB: held-out set v2, 466 tasks

ModelTrained for GruxMeasuredRightShare, 95% intervalHidden-instruction cases passed
grux-local:4byes2026-10-23398 of 46685.4%, 81.9% to 88.3%10 of 70
grux-local:4b-v2yes2026-10-23442 of 46694.9%, 92.5% to 96.5%53 of 70

Ollama 0.40.8, MLX runner, one request at a time, thinking off as Grux sends it. Raw JSON: v1.json.

The same Ollama tag, qwen3.5:4b, got 392 of 464 in the weekly table and 396 of 464 on the Mac mini, Apple M4, 16 GB. Same tasks, but a different machine, Ollama version and runner, and so a different build of the weights, which is why no table on this page mixes machines.

The same Ollama tag, qwen3.5:9b, got 396 of 464 in the weekly table and 400 of 464 on the MacBook Pro, Apple M4 Pro, 48 GB. Same tasks, but a different machine, Ollama version and runner, and so a different build of the weights, which is why no table on this page mixes machines.

Every result file

All 3 weekly result files at commit 3b6512e, newest first. A file is never edited once it is published; a new score is a new file.

ScoredModelSet v1, of 464Set v2, of 466Raw
2026-11-10qwen3.5:9b396357JSON
2026-11-10qwen3.5:4b392362JSON
2026-11-10mimo-v2.6:9b367354JSON

How this page is rebuilt

Each week the Grux Local lane looks for new open models at Mac sizes and scores each one it can run on both held-out sets, beside the stock Qwen 3.5 rows it last scored. Once its result files are published to the grux-local repository, this page is rebuilt from them at one pinned commit, and the rebuild refuses any file that did not finish, whose set hash or size does not match, whose task families do not add up to its total, whose stored interval differs from a recompute, or whose model has no open licence.

Raw files

Questions

What does the Grux Local scoreboard measure?
How often a small open model does a job Grux hands a local model correctly, on Grux's held-out sets of 464 and 466 tasks, scored by Grux's own parsers. It does not measure general ability, and it compares no model with a hosted one.
How were the latest scores made?
On one NVIDIA H200 GPU in the cloud, rented by the hour, with Ollama 0.40.16, llamacpp runner, thinking off, a 16,384 token context, one request at a time. On set v1, qwen3.5:9b got 396 of 464 right (81.8% to 88.3%), qwen3.5:4b 392 (80.9% to 87.5%) and mimo-v2.6:9b 367 (75.2% to 82.6%).
Why are the Grux Local numbers in their own tables?
Grux Local is trained on jobs shaped like these and was measured on Macs, not on the cloud GPU, so its tables show before and after training on one machine and never share a table with the weekly scores.
Can I check a number myself?
Yes. Every row links its raw JSON in the public grux-local repository at commit 3b6512e, and both set hashes are pinned in recipe/check_prompts.py at the same commit.
Download Grux AI 3.2.0 Read the source

Free, MIT licensed. macOS 14 or later, Apple silicon. 28.4 MB, signed and notarized by Apple. No account, no server, no subscription.