* make the labs card copy plain
Rewrite the Labs card titles and lines in words a regular user understands:
YOLO mode says the message sends itself, Live text and Failure notices name
the small recording indicator, Vocabulary help says which speech models it
affects, and the key-side cards name Option, Command, Shift, and Control.
Audit every other card, updating the CLI descriptions, all nine translated
languages, the website lab catalog, the feature docs, and the render goldens.
* fix labs copy review findings
Restore the ISO qualifier on the section-key card, spell out that
double-tap and hold-through shortcuts contain no letter or number key,
cover all Global mode stages in the API text card, and name the print
command in the print-start copy. Restore the developer API card titles,
fix the Annotate capture wording, and retranslate the affected strings.
Remove every replaced translation key and stale lab-name reference.
* fix second labs copy review
Update the live typing test and YOLO goldens. Add a Windows variant of the
hold-through-keys copy naming Ctrl, Alt, Shift, and the Windows key. Remove
the last unused rewrite-by-voice translation key, keep Annotate untranslated
in the replay title, and clean the remaining old lab-name comments.
* use the Polish Annotate pane name in its replay title
Polish calls the Annotate pane Adnotacje, so the Annotate last 15 seconds
title says Ostatnie 15 sekund w Adnotacjach again. Other languages keep
Annotate because their pane name is Annotate.
* Sound volume is a slider (t1489)
* Keep the slider test's presses on the track (t1489)
* Drop the slider test's ambiguous a11y lookup (t1489)
* Show the sound volume slider inline in its row (t1489)
* Describe the sound volume slider in the feature map (t1489)
* Keep the slider test's presses on the narrower track (t1489)
* fix(linux): say when live typing and live text can't show words
Live typing's Labs card now asks the Wayland registry once at window load;
without zwp_input_method_manager_v2 (GNOME) it stays listed, disabled while
off, with a note that this desktop offers no input method it needs and
dictations paste normally. `hex labs` prints the same note in its list and
after `hex labs on live-typing`, without refusing the toggle.
Live text's card names the catalog's streaming models when the selected
model can't stream, and on Linux says when Speech engine is set to CPU. A
capture that wanted live words but opened no stream logs why once per
capture, and a stream begun on a model that can't stream says so instead of
failing silently.
Docs updated for Labs, dictation, and the Linux beta.
* fix(linux): review fixes for the live typing and live text notes
An imported model's catalog entry says it can't stream, but its GGUF is only
checked when it loads: the Live text card never judges one, and the capture
log blames the device instead of the model.
The Live text card shows its note under the description, not instead of it,
and names only streaming models that take the saved language (or none when
none do). Live typing's CLI note is only for Wayland with a compositor that
has no input method Hex can use, and never for a managed feature.
The capture log says "no live stream yet" rather than claiming it for the
whole capture, and a stream request on no loaded model no longer says the
model can't stream.
* docs(labs): tidy the live typing checks list
* fix(linux): second review fixes for the live notes
The capture log says only that no live stream has opened yet and why, with no
claim about the rest of the capture or the paste. Row's doc comments now say
a note joins the description and that a desktop without the input method also
locks the switch.
The engine's stream log leaves model_streams off for an imported model, whose
GGUF alone decides. The CLI note uses the card's exact wording, and the Live
text suggestions skip models that aren't available here.
KDE's color-scheme portal describes window colors, so a mixed theme such
as Breeze Twilight picked a black mark for a dark panel. Bump rune for
TraySpec::icon_name, write anomaly.hex-symbolic.svg into the user's
hicolor theme at startup, and serve that name beside the pixmap so Plasma
6, GNOME's AppIndicator extension, and Waybar draw the mark in their own
text color. The icon keeps the old white/black default for hosts that
don't recolor, and the installer removes only a marked file.
Goldens follow the rune bump.
* Add Labs terminal paste shortcut for Windows and Linux
* fix windows build: drop the unused key_down from input/modifiers
* allow the terminal-paste shortcut code to go unused on macos
* mask the second shortcut's menu modifier on auto-repeats
the mask was only set on the first press, so process_button cleared it on each
repeat key-down and a held capture over the repeat delay leaked a bare alt/win
release. set it on every trigger key-down like the dictation key and paste
last do.
* keep side_matches private
* keep the shortcut and dictation helpers under the source cap
windows/dictation.rs, rune_ui/general.rs, and linux/dictation.rs crossed 1,500
non-test lines after the rebase. move the registered-shortcut tables and the
General pane's shortcut rows into submodules, and refresh the Linux Labs
golden for Transform typed text and Terminal paste shortcut.
* call the global setting Terminal paste in typed text's refusal
the lab now owns the name Terminal paste shortcut, so the typed-text errors
and log line must name the global paste_with_shift setting instead.
* drop the terminal paste lab's unused encoded bit
no accessor reads it and no other lab has a bit without a reader; the feature
reads its saved switch directly through Feature::on.
* raw dictation has a hex command; the terminal paste shortcut does not
* feat(linux): labs transform typed text shortcut (#1519)
* fix(linux): harden typed-text clipboard handling
* fix(linux): keep dictation clipboard fallback, sync typed-text keybinding
* refactor(control): keep shortcut text in its own settings module
settings.rs crossed the 1,500-line limit when Labs added the typed-text
key; the shortcut text parsing and formatting is the one self-contained
concern, so it moves to settings/hotkeys.rs unchanged.
* add a Labs toggle for Annotate overlays on GNOME
Rune won't back an overlay with an XWayland window when it asks for keys
on demand, so Annotate's recording capsule, ink, and picker never show on
GNOME Wayland: a capture records with nothing on screen. With Labs ›
Annotate on GNOME (`labs.gnome_annotate`, off by default), open them on an
already running XWayland like the meeting capsules do, with the same
checks at each show and without ever starting XWayland. The ink is made
with pointer regions and no keys, since it must take the pointer later
and Rune refuses an OnDemand overlay there; Esc can't stop drawing, so
the capsule's pen button or the Annotate key does.
idea and diagnosis from @pkkid in #1526
* Bump Rune to f2fb51ea
XWayland overlays now update their input shape on every drawn frame
* fix the Annotate lab copy and the XWayland checks
Esc can't stop drawing on the GNOME path, and a tap of the Annotate key
stops the recording, not the pen; the capsule's pen button or letting go
of a held key ends drawing. Use each language's existing name for the
Annotate feature, evaluate the ink's XWayland check once at install, and
skip the picker's check when nothing shows.
* linux: adopt the wayland display behind an xwayland DISPLAY (#1505)
* linux: share wayland adoption with the launcher, keep x11 logins
* linux: only a wayland or unset session type adopts behind DISPLAY
* fix(linux): name the missing wl-copy before a Wayland paste
* fix(linux): address review on wl-copy warning
* fix(settings): show the wl-copy notice apart from dictation failures
* linux: live typing through the input method (labs)
* live typing: gate typing demand to linux
* live typing: fix finish claims, session guards, and control delivery
* live typing: start on intentional captures
* live typing: keep begun sessions controllable after an abandoned finish
* linux: dark tray mark on light panels
Read the desktop's color-scheme from the settings portal when the tray is
created, and draw the mark black when it explicitly prefers light. Move the
shared recolor from the Windows tray beside the shared tray menu.
* docs: note linux tray mark check and limitation
On a Wayland compositor without layer-shell (GNOME), the recording offer and
recording capsule can open on an already running XWayland with Labs ›
Floating meeting capsules on GNOME (gnome-meeting-capsules, off by default),
through Rune's new OverlayOptions::xwayland_input. Off, or when the overlay
still can't open, the offer opens the Meetings pane as before (#1271), whose
note now names the lab. Rune pin bumped for anomalyco/rune#85.
Thanks @lgwacker for the analysis in #1274 and rune#85.
The local API's running-app dictation now records on the Linux listener with
the macOS contract: owner tokens, the ten-second lease, levels, the audio tap,
and the same error codes. The protocol, completion record, lease and meter move
to dictation::service, which both platforms share; Linux drives them through
ServiceDictations. A client's dictation and a shortcut or hex dictation capture
never end each other: a start while the shortcut records is dictation-busy, and
the shortcut does nothing while the client's dictation records.
* 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)
* Linux: new KDE Plasma setups dictate with Ctrl+Alt+Space; KRunner keeps Alt+Space (#898)
* KDE: wait for the shortcuts dialog; a bind left unapproved asks again instead of keeping keyless shortcuts (#898)
* Docs: KDE shortcut dialog and recovery (#898, #896)
* Speech engine: remember a GPU that failed per device and driver, Auto stays on the CPU for it; Settings › Speech engine Auto/GPU/CPU (#856)
* clippy
* doc
* log the device key and driver on load
* Speech engine row under Dictation
* Docs: speech engine and the GPU record (#856)
* AGENTS: gpu_health
* Speech engine row: not in macOS fixtures
* Linux: launcher and autostart entries follow a version manager's shim; a stranded launcher entry points at this Hex (#810)
* Shims checked, deleted executables, migrate to the shim before a prune, one Exec escaping, stranded fallback yields to a package; docs (#810)
* clippy
* Shim: root-owned version manager allowed, /home links resolved, --help names Hex
* Linux: use the Background portal for running in the background and Launch at login (#812); fallback entry written once (#810)
* test names
* Docs: Background portal and Launch at login (#812)
* Background portal: only once registered (1.20+), symlinked entries are the user's, serialize entry writes and login changes
* doc comment
* 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
* Wayland paste: close the idle RemoteDesktop session, reopen with the saved grant (#718)
* Wayland clipboard: restore through ext-data-control too (#719); docs
* fmt, lockfile
* 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
Records like the dictation shortcut and pastes the transcript as heard,
skipping replacements, corrections, transformations, and rewriting. Unbound
by default; set in the Output pane, raw_dictation_hotkey, or
hex dictation start|toggle --raw. History keeps it as Raw.
Suggested by @ksajan.
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
Linux reads the focused application on Wayland from the compositor's
foreign-toplevel list (named by its .desktop entry) and the focused page's
address through AT-SPI on X11 and Wayland. macOS reads the front tab of
every scriptable browser (Safari and Chromium dictionaries) and any other
app's focused AXWebArea, instead of only Brave.
On a Wayland compositor without layer-shell (GNOME's Mutter), Rune now opens
only the HUD as an override-redirect, click-through X11 window on XWayland
(Rune 9983acad). The rest of Hex stays on Wayland, so portal shortcuts keep
working. Without XWayland, the #466 status and log remain.
A saved XAUTHORITY whose file is gone after a reboot is replaced at startup by
the user manager's current value, else dropped.
Fixes#465