Skip to content

Mightling v1.6.4

Choose a tag to compare

@github-actions github-actions released this 15 Oct 13:37

Mac desktop app (preview, unsigned)

Mightling-1.6.4-arm64-preview.dmg (Apple silicon) and Mightling-1.6.4-x64-preview.dmg (Intel) are a preview of the desktop app for macOS 12 or later, a client of a Mightling node on your network. They are signed ad hoc only, with no Apple Developer ID and no notarization, so macOS refuses to open the app the first time. Drag Mightling to Applications, try to open it once, then allow it in System Settings → Privacy & Security → Open Anyway (on macOS 14 and earlier, Control-click the app and choose Open instead). Or, in Terminal: xattr -dr com.apple.quarantine /Applications/Mightling.app. Check the dmg against SHA256SUMS first; steps in docs/desktop.md.

The model server runs SGLang v0.5.21. The default model's recipe pins lmsysorg/sglang by digest; the pin moves from v0.5.19 to v0.5.21. The old image skipped a save of the recurrent state when accepted draft tokens crossed a checkpoint, so a later prefix-cache hit could pair the new attention cache with a stale state (SGLang #37817/#37818, fixed in v0.5.20). Before the move, both images were probed on a GB10 for wrong answers with the same greedy requests and seeds: 48 at one stream, 200 at two, 304 at eight, and 32 two-turn conversations over a long prefix; 0 wrong on both, and the new image answered a few percent faster (67.6 / 121.8 / 297.7 tokens per second over all streams at 1 / 2 / 8, against 63.7 / 112.7 / 269.1). One launch flag changed name with the image (--cuda-graph-max-bs became --cuda-graph-max-bs-decode; the value is the same); nothing else in the launch line changes. A node that updates pulls the new image (33.7 GB) at its next ling-admin server start, before the running server is replaced; until then it serves on the old one.

The Windows client is back. install.ps1 installs ling.exe and its commands on Windows 11 (Arm64 and x86-64), as 1.5.1 did; 1.6.0, 1.6.1 and 1.6.3 shipped without them, only because the release workflow left the Windows build off by default. The assets are the names install.ps1 asks for: ling-<target>.gz, ling-<target>.sha256sums, codex-code-mode-host-<target>.gz, and the optional ling-search, ling-fetch, ling-code, codex-windows-sandbox-setup and codex-command-runner, for aarch64-pc-windows-msvc and x86_64-pc-windows-msvc. Still a preview: the programs are not code-signed, so Smart App Control must be off to run them. The release's signed checksum list covers the Windows files like every other, and ling update checks it on Windows too; install.ps1 checks the per-target sums but not that signature yet (install.sh and ling update do), a gap left for a later release.

Full Changelog: v1.6.3...v1.6.4