Skip to content

v0.2.3 - both defaults on, and the model list tells you more

Choose a tag to compare

@tmxkzm1925-max tmxkzm1925-max released this 09 Aug 06:19
· 38 commits to main since this release

A convenience patch. Same engine and repacker binaries as v0.2.2; no new measurements.

What changed

  • Arch-template is on by default - an unlisted GGUF of a known architecture now serves without any switch, labelled experimental. Turn off with -ArchTemplate off.
  • Warm-up is on by default - the server warms its serving path once, right after ready. Restore the old behaviour with -Warmup off.
  • The model menu labels each entry - [catalog], [template: <arch>], [unsupported] or [identify pending], read from the file's own header, so you can see the likely route before you pick.
  • A warmed start says so - the status screen reports the performance gate as [unmeasured] on a default start, because every published number is a cold-cache run. -Repro and -Smoke force warm-up off so benchmark runs stay comparable.

Good to know

  • Warm-up warms the serving path, not your prompt - a large system prompt still pays its full prefill on the first question. -Warmup file:<path> precomputes a real prompt; a graceful stop still saves the session's KV for the next start.
  • The menu labels are a good guess, not a verdict - the real decision at start also weighs shards, sizes and the source pin.
  • No integrity check moved: architectures without a template are still refused, and the repack still waits for your y/N. If your automation assumed the old defaults, pass -Warmup off or -ArchTemplate off.

Details: README · docs · TECHNICAL.md

Verify the download

One paste, nothing to compare by eye - in Explorer, open the folder that holds both downloaded files, right-click empty space > Open in Terminal (PowerShell), then paste; it prints OK or MISMATCH:

$e=((Get-Content .\SHA256SUMS.txt -Raw).Trim() -split '\s+')[0];$a=(Get-FileHash .\moe-direct-v0.2.3-win-x64.zip -Algorithm SHA256).Hash;if($a -eq $e){'OK: hash matches'}else{'MISMATCH: download again'}

If you skip it, you are still protected: the launcher re-verifies every file inside the extracted bundle against its sealed manifest on every start, fail-closed. Only this paste establishes that the zip itself is the released one.


Erratum (2026-08-14): this tag's source snapshot accidentally carries the v0.2.2 launcher; the zip above was always the correct v0.2.3 build (SHA-256 unchanged), so downloads are unaffected. For source that matches the zip, use v0.2.3-corrected.