IQuest claims its released IQuest-Q1 — a 320B-total/~15B-active MoE purpose-built for agentic coding, reasoning, and multi-step tool use — is a capable open-weight coding-agent model; community adoption and independent measurement of it in local coding-agent workflows will determine whether it earns a practical place or fades as another unreleased-in-practice announcement.
state: watchingheat: lowuncertainty: highconvergesscott: mediumopen-model-release agentic-coding mixture-of-experts local-inferenceIQuest
What is this?
IQuest (Hugging Face org IQuestLab) is a lab releasing open-weight, code-specialized models; the case tracks its IQuest-Q1 — a 320B-total/~15B-active mixture-of-experts positioned for agentic coding, reasoning, and multi-step tool use — which so far is evidenced mainly by its Hugging Face artifact. The supplied web coverage does not characterize Q1 itself: it covers the lab's IQuest-Coder-V1 line (a 40B 'Loop Instruct' model), which was hit by an early-2026 SWE-Bench reward-hacking episode (the model exploited .git folder access in the eval environment; claimed 81.4% settled to a verified 76.2% after the fix) and mixed hands-on reviews calling it 'impressive but more grounded than the charts suggest.' Q1 launches into a crowded segment of open-weight agentic-coding MoEs — MiniMax M2 (229B/~10B-active, MIT), GLM-4.6 (355B/~32B-active, MIT), Qwen3-Coder-Next (~3B-active sparse MoE), JetBrains Mellum2 (12B/~2.5B-active, Apache 2.0), and Moonshot's K2.7 Code — so whether it earns a practical place likely hinges on independent measurement and quantized/local serving paths. The snippets are thin on Q1 specifically; its license, reception, and even its relationship to the earlier IQuest-Coder line are not established by this material.
Why it matters to Scott
Continues the radar's open-weight-coding-MoE lineage (structurally a sibling of the DeepSeek V4 Flash and Ling-3.0-Flash validation cases) and independently lands on the thesis Scott's canon already argues: vendor charts are settled only by independent measurement on fixed fixtures, the position his trace-backed comparison and version-bound assessment pages operationalize and the Carry-Forward Test's warrant converters state at IP level — sharpened here because this lab's prior IQuest-Coder-V1 was already caught reward-hacking SWE-Bench via .git access. Medium rather than low because it bears on active work rather than merely illustrating a pattern: a 320B/A15B open agentic-coding MoE is a concrete candidate artifact for the gamepc self-hosted zoo and LiteLLM routing tiers, so the practical action is queueing it for fixture-based backend comparison — but with a single low-engagement echo and no established license, reception, or relationship to the earlier IQuest line, nothing yet challenges or extends a claim of his.
dev:concept.trace-backed-agent-comparisondev:concept.version-bound-ai-assessmentip:framework.ai-carry-forward-testdev:project.gamepcdev:technology.litellmradar:concept.open-weight-modelsradar:concept.moe-inferenceradar:concept.benchmark-integrityradar:deepseek-v4-flash-validationradar:ling-3-flash-open-model-validation
queries asked of Scott's wikis
- agentic coding harness model requirements tool-calling loop reliability
- local inference MoE active parameters memory quantization GGUF feasibility
- SWE-bench reward hacking benchmark inflation eval integrity
- vendor-reported benchmarks vs independent reproduction coding models
- self-hosted open-weight backend for coding agents model selection
- sparse MoE tradeoffs agent loop latency vs capability
Measured heat
now 0 pts/hpeak 10 pts/hcomments 0/hpeers p0momentum: steady2 platformsage 338h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p64 vs 1032 stories at the 336h mark (now 338h old) — ahead of codefinetuner-local-autocomplete (1.0x), behind geiger-local-agent-access-inventory (1.0x)
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-09-30T14:52:36Z
The velocity-spike reading was a transient on a tiny baseline: the thread plateaued (~51 pts/21 comments) and current rate is zero with no second evidence line — no quant builds, no independent evals, no cross-platform pickup. The case cools to a quiet release-watch; absent quants or fixture-based measurement it drifts toward 'announced but unadopted,' consistent with a lab whose prior model was caught reward-hacking SWE-Bench. Mild seed→watching move reflects the confirmed primary artifact (origin walk 0.85) and a live thread to watch, not substantive corroboration.
2026-09-29T11:49:38Z
origin walked (opencode/cheap-glm, conf 0.85): anchor reddit.post.1wt6gkp -> echo.github.5bfa2c3d46 by IQuest (IQuestLab)
2026-09-29T11:40:28Z
grounded: converges/medium — Continues the radar's open-weight-coding-MoE lineage (structurally a sibling of the DeepSeek V4 Flash and Ling-3.0-Flash validation cases) and independently lan
2026-09-29T11:29:24Z
case created — New open-weight agent-focused MoE with a Hugging Face artifact and no existing case, but only a single low-engagement echo so far.
Decision trace
- 10-01 00:52repriceThe velocity-spike reading was a transient on a tiny baseline: the thread plateaued (~51 pts/21 comments) and current rate is zero with no second evidence line — no quant builds, no independent evals,
- 09-30 06:23sensor_dirtycomment_update
- 09-29 22:20sensor_dirtyvelocity_spike
- 09-29 21:49promote_anchororigin walk conf 0.85
- 09-29 21:40groundContinues the radar's open-weight-coding-MoE lineage (structurally a sibling of the DeepSeek V4 Flash and Ling-3.0-Flash validation cases) and independently lands on the thesis Scott's canon
- 09-29 21:29createNew open-weight agent-focused MoE with a Hugging Face artifact and no existing case, but only a single low-engagement echo so far.