Skip to content

v2.46.0 — a Settings window you can actually see

Released 2026-10-24. Upgrade:

sudo snap refresh yazses     # snap
pipx upgrade yazses          # or: uv tool upgrade yazses
scoop update yazses          # Windows

Restart the daemon afterwards (yazses restart).

The Settings window is a sidebar of pages

The old window stacked every control in one column and gave the list of capabilities whatever height was left over, which at the default size was about 70 px. The largest part of YazSes was a slit at the bottom of the window.

It now has a sidebar with six pages: General (the hold-to-talk key), Speech, Audio, Features, Hands-free and Updates.

  • The Features page uses the whole window. A search box sits on top. Beside the rows there is a category list that shows how many capabilities are on in each (6/23). While you search, those numbers become match counts, and a category with nothing left leaves the list. The filter syntax (tier:rec, on:, off:) is written under the search box instead of living only in a tooltip.
  • Apply and Restore defaults never scroll away. They sit in a footer. The snap-permission warning stays pinned above every page.
  • You can see what is unapplied. A dot beside a page name means that page holds changes you have not applied, and a capability you ticked but have not applied gets a coloured bar on its left edge. The dot goes when you press Apply or put the value back.
  • Keyboard: Ctrl+1 to Ctrl+6 jump to a page, Ctrl+F goes straight to the search.

Nothing about what the window does has changed. Staging, Apply, the restart offer, installs, the experimental confirmation and Restore defaults behave as before, and no config key or command changed.

"Apply and restart" no longer leaves YazSes stopped

On a systemd install, yazses restart begins with systemctl --user stop yazses. When the restart was launched from the tray or from the Settings window, it was itself a descendant of the daemon, so systemd killed it together with the rest of the service before it reached the start step. The daemon stayed down, and the Settings window died in the same stop, so it could not tell you. Typing yazses stop and then yazses start in a terminal worked, because a terminal is outside the service.

The tray now starts Settings and its Restart item in a systemd-run --scope of their own, and yazses restart and yazses start do the same when they find they are inside the service. Without systemd-run, off Linux, or from a terminal, nothing changes.

What was checked: a throwaway systemd unit reproduced the self-kill and showed the scope surviving it, and the tests cover the cgroup detection, the command line and both commands. What was not: "Apply and restart" on a live daemon from the tray, end to end. Also, the first restart after you upgrade still runs your old tray, so do that one from a terminal with yazses restart.

Smaller

  • The Thai page was reviewed by a native speaker. It was a machine-assisted draft. Thank you, @Warayuth014 (#665).
  • Release jobs: the Docker and Chocolatey jobs no longer race what they depend on. They failed on v2.44.0 and v2.45.0 and each needed a rerun. This changes how releases are built, not what you install.

The complete list is in the changelog.