* use OpenCode's default model for meeting summaries
Meeting titles, summaries, and live chapters with no meetings.opencode_model
post one request with no model field, so OpenCode answers with its own default
and the transcript never reaches a provider the person didn't pick. The ranked
fast models stay for dictation rewrites and voice prompts.
The summary model picker's automatic entry and its invalid-value note say so,
with translations, and the meeting docs follow.
Move the one-shot generation transport into dictation/processor/generation.rs
to keep processor.rs under the 1,500-line cap.
* docs: cover OpenCode's default model in notes and rewrites
The meeting notes footer list now names the case with no chosen summary
model: "Written by OpenCode's default model" (#1125).
The dictation map carries the #1123 fallback the meeting map no longer
describes: the ranked rewrite models are cached per service, any one failing
drops the cache, and when all of them fail OpenCode's default answers.
GENERATE_ENDPOINTS stays inside its module; nothing outside it names the
routes.
* feat: labs appearance setting to force light or dark (#1590)
* fix: appearance lab title bar and review fixes
* fix: re-apply the forced title bar after windows settings broadcasts
* fix: only re-apply a forced caption, and drop the subclass on destroy
* test: refresh labs goldens after rebase
* feat(windows): labs toggle to use opencode running in wsl (#1564)
* fix(windows): bound and cache the opencode wsl lookup
* fix(windows): share and validate the opencode wsl lookup
* fix(windows): age-limit shared wsl lookups and retry workspaces
* cli: select the model after an offline `model install`
With Hex stopped, `hex model install` downloaded and verified the model but
never wrote the selection, so `model status`, `check`, and `transcribe` kept
using the previous one, and no message said so.
The offline branch now selects it as the app's own switch would: a Hex that
started while the download ran takes the choice over `model use`, otherwise
the selection is saved under the Linux service lock `settings apply` uses,
so a starting Hex is never written behind. An already selected model is left
alone, so login-time installs don't rewrite settings.json.
Docs say the offline install selects now, and a new app_settings test covers
the persisted round trip keeping unrelated settings.
* cli: wait for a starting Hex before selecting an installed model
`model install` with no Hex running saved the selection under the
service lock, and failed at once when a Hex already held it. Wait for
that Hex to answer instead, as `settings apply` does, through one
shared hand-off so the two paths can't drift. An unchanged selection
answers without taking the lock.
* Windows: ship hex.com, a console entry point beside the GUI hex.exe, on PATH
* lock, fmt, legacy adoption
* clippy
* build hex-console in its own cargo run: -p hex is ambiguous with the hex crate
* hex.com returns once the app starts; Ctrl+C only; install script and Setup replace a running hex.com; hex-console checks in Compile
* fmt
* installer test: exit 0 once every check passed
hex.exe is now a GUI program. Commands run from a terminal join it
(AttachConsole) and print there; the app leaves it after startup errors
have had their chance to print. Rune 31dbcad cloaks a window until its
first frame presents. Release checks assert the GUI subsystem.
* windows: delay-load vulkan-1.dll and fall back to CPU without a Vulkan 1.2 driver (#1240)
* windows: note vulkan-1.dll is delay-loaded in restrict_dll_search
* General: one Shortcut mode choice with a modal (t1218)
Hold or double-tap, Hold, Tap and Double-tap replace the Shortcut mode,
Double-tap to lock and Double-tap only settings. The row sits under the
shortcut and opens a modal with each choice's keys and a looping
key/recording timeline; Double-tap says it needs a shortcut with a key.
* Shortcut mode: scenes and Double-tap's reason on every OS (t1218)
* Shortcut mode: goldens (t1218)
* Shortcut mode: scenes live in shortcut_mode.rs; keep rune_ui.rs under its limit (t1218)
* Format dev's permissions and platform settings (t1218)
* Shortcut mode: picker goldens over the new row (t1218)
* Onboarding: stay on the model list once a pick is ready, and Back returns to it
* Docs: the model list stays once ready, and Back returns to it
* Test: allow the advance beat under load
* Make the new onboarding the one first run on every build and OS
* Drop the tour's Back and page dots, which only the old view used
* French for the first run's strings
* Test the story's stopped download names why and offers a model file
* Golden: the stopped download names why and offers a model file
* Remove dictation cancel: Escape ends nothing (#786)
* Format and refresh the sound sets and commands goldens
* Release Escape before finishing in the held-capture test
* Merge recognition hints into the shared vocabulary
* Drop the unused text field helper
* Drop unused imports
* Cohere stands in for a model that ignores the vocabulary
* Update the picker golden for the Uses vocabulary badge
* x86_64: keep ggml on x86-64-v3 and refuse older CPUs with a clear message (#592)
Reverts #595's Ivy Bridge floor: it slowed CPU transcription for everyone. ggml goes back to its x86-64-v3 defaults (AVX2, BMI2, FMA, F16C). Hex's own Rust stays baseline x86-64, and the first thing main does on Linux and Windows x86_64 is check AVX2/BMI2/FMA/F16C with is_x86_feature_detected!. Without them Hex prints and shows "Hex needs a 2013 or newer processor (Intel Haswell / AMD Excavator or later) with AVX2. This PC's processor isn't supported." (a native MessageBox on Windows; stderr, which the journal logs, and zenity, kdialog or notify-send on Linux) and exits 1. Every command is covered except --version and --help, which installers and the updater run. ggml-cpu has no static constructors, so nothing runs v3 code before main.
The release guard now asserts the opposite: ggml's CPU libraries must hold AVX2 and FMA (the build targets v3) and no AVX-512 or AMX. Docs state the requirement.
* cpu_floor: harden DLL search first; no dialog under systemd, in a terminal or for hex service; guard rejects AVX-VNNI
* cpu_floor: always exit 1; Windows always shows the message box; Linux skips the dialog in a terminal, under NOTIFY_SOCKET, or for hex service
* Talk only to a running OpenCode service; never spawn or probe a CLI
* wip
* wip
* Golden for OpenCode not running
* clippy
* fmt
* General's microphone meter wakes the window only while its bars show a level
* Feature map: the microphone meter rests in a quiet room
Linux and Windows now hand the local API's POST /control to the shared
control host, so the CLI reaches every OS through local-api.json and
call_control. The Linux socket's Request::Control and the Windows named
pipe (windows_control) are gone.
* One hex control CLI and protocol on every OS
One command tree (control::cli) on macOS, Linux, and Windows, carried by
each OS's owner-only transport: the macOS local API, the Linux socket's
Request::Control, and a new Windows named pipe (windows_control) that only
this user's SID can open and whose server the client verifies. Linux and
Windows share one host (control::host) through thin adapters; what an OS
can't do answers unsupported at runtime.
Windows gains dictation (with stop --print), paste-last, quit, restart,
start, a live status, and every annotate command; Linux and Windows gain
settings, model, window, vocabulary, history clear, check-for-updates,
launch-at-login, onboarding reset, logs, commands init|check, and annotate
status. hex status reports the OS's capabilities, settings name the
capability they need (set refuses, list marks), and a parity test requires
a recorded reason for every capability that differs across OSes.
* Windows control pipe: always hold an unconnected instance; check the client's user
* Shared control: meetings, history, and mcp on every OS now that the meetings store does
* Parity: error tone, Windows modifier sides, practice dictation, tray menu, Linux launch at login (WIP)
* Docs, formatting, and tests for the parity UX gaps
The site's download buttons and the README/docs links name /hex/download/<target>, which the site Worker redirects per request to the release service's stable alias once stable.json exists and to the dev alias until then, so nothing needs switching back. The page labels the build ("Dev build 0.0.0-dev-N", with a note that it updates from the Dev channel) and refreshes the version from the live manifests. The Linux button names the site's own install-linux.sh. The anomalyco/homebrew-tap cask now installs the dev alias (version :latest, sha256 :no_check, auto_updates); the Release workflow's stable Homebrew job replaces it with a versioned cask at the first stable release.
From the 2026-10-29 security review:
- H1: Release signs each Linux executable with Anomaly's ed25519 key (HEX_RELEASE_SIGNING_KEY, .github/release/sign-linux.sh, which refuses a key that does not match linux-signing.pub) and publishes the signature as the linux-<arch>-sig target. The updater (updater/linux.rs SIGNING_KEY) and install-linux.sh refuse an executable without a valid signature over its SHA-256, before downloading it. Installed builds that predate this ignore the extra target, so the transition needs nothing from them.
- H3: the installers move to the locked .github/release/ (CODEOWNERS @thdxr); the Installers workflow publishes them from a sparse checkout of that directory.
- M1: the release service client is vendored as .github/release/release-client.sh instead of piping anoma.ly/release/client.sh into bash.
- M2: check-windows.yml gets permissions: contents: read; every third-party action is pinned by SHA.
- M3: resolve_url accepts only URLs on the manifest's host.
Dax made Dot scope (the dot-scope experiment from #264) the default. The glossy capsule's shader, uniforms, styles, and HUD Lab controls are deleted, so the HUD has one look. Dot scope gains a green Voice Action look and a 200 ms minimum processing look; failure stays coral and cancel fades. Its own auto level keeps a hot microphone moving, as #360 did for the capsule. An experiments file or HEX_EXPERIMENTS naming dot-scope is ignored silently. HUD Lab tunes Dot scope in debug builds and, in release, while the playground experiment is on; the playground lists HUD stories whenever it is on.
Ukrainian joins the Interface language picker on every OS, and every string
in the translation table has a Ukrainian column. macOS permission and
System Settings names follow Apple's Ukrainian labels so users can find them,
and "Voice Action" stays in English as in the other languages.
Co-authored-by: Dax Raad <d@ironbay.co>
* Drop glib/gio and tray-icon: Rune tray and file dialogs, zbus for the portal and MPRIS
* Drop glib from packaging, Nix, CI and docs; Rune tray and dialogs in the docs
* fmt; Nix hash for Rune 07520d0
Port dictation_indicator.metal to WGSL (rune_hud.wgsl) and draw it on the GPU
from a Rune overlay compositor shared by Linux and Windows (rune_hud.rs). This
replaces the Windows CPU shader port and the Linux text pill, adds Dot scope
with its auto level and processing looks when the dot-scope experiment is on,
and feeds the Linux HUD the listener's meter and job outcomes.
* Run personal commands in embedded QuickJS instead of Bun
Hex now runs ~/.config/hex/hex.config.ts in-process: rquickjs on one worker
thread, TypeScript erased to same-position JavaScript with oxc's parser,
per-call time limits and a runtime memory limit, and no filesystem, network,
process, or timer API. Handlers return actions that Hex validates and runs on
its native executor. The Bun host, managed SDK provisioning, bun update, the
sdk/commands workspace, and their scripts and CI steps are gone; Hex writes
hex.d.ts typings instead, and hex commands check replaces bun run check.
Plan and measurements: docs/plans/quickjs.md.
* Spell out a range check that a new dependency's impls made ambiguous
* Rename voice-control to hex everywhere, without migrations
The Cargo package and binary are now hex, every OS keeps its data in a
hex folder, and VOICE_CONTROL_* variables are HEX_*. Hex is a fresh
app: the macOS voice-control rename, its symlink, and the Windows and
Linux beta settings imports are gone. The Windows installer gets a new
AppId so it never takes over an old voice-control install's entry.
* Format
* Drop the Windows paste-last default only the beta import used
The native caption draws no icon or title (WTNCA_NODRAWICON|WTNCA_NODRAWCAPTION) and DWM paints it the theme's bg_deep (DWMWA_CAPTION_COLOR, Windows 11), repainted when the system theme switches. The taskbar and Alt-Tab keep the icon and title; the frame, resize edges, and caption buttons stay native.
FreeConsole left stdout/stderr holding closed console handle values. Windows reuses them for later objects, so once a read-only file took the value, the listener's 'Hex is ready' println! panicked and Settings showed 'listener worker stopped unexpectedly' on every Enable. A writable file taking the value would have received printed and logged text.
Null the console std handles after FreeConsole (std then discards output; redirected handles are kept), and record every panic with thread and backtrace in process.log, where the GUI's lost stderr hid this one.
Work lands on dev, the default branch. production holds what was released
(app-v2.3.1) and moves only by a fast-forward from dev. Pushes to dev run the
checks, test builds, and the dev site deploy; stable releases run only from
production or an app-v tag, and the TypeScript SDK's version pull request
targets dev while publishing waits for production.
The Release workflow uploads each target and the release to anoma.ly/release (dev.anoma.ly/release for staging) with curl and its GitHub OIDC token, records the AUR, Homebrew, and Nix distributions, mirrors the files to GitHub, and builds hex-bin from the published file. The ed25519 feeds, appcast generation, and Sparkle ZIP naming are gone; the 2.3.1 feeds stay frozen. Builds and installers use the release service names, the installers read the stable manifest and write the direct-install receipt, and the site reads its download links from the manifest.
One site/cloudflare.config.ts defines the production Worker hex (anoma.ly/hex, bucket hex-production-files) and the dev Worker hex-dev (dev.anoma.ly/hex, bucket hex-dev-files), deployed only from CI with cf deploy --prebuilt --mode. The Worker serves the site and the release bucket; apps, scripts, the release workflow, and docs use https://anoma.ly/hex/files. Staging releases publish to the dev bucket; stable releases deploy the production site.
A staging channel dry-runs the whole pipeline under staging/<run-id>/ with a draft GitHub release; uploads use the bucket-scoped R2 S3 credentials. Adds the hex-voice-bin AUR package and docs/releasing.md.