Server server2-20261105-01

Official server release from quicktui-mono@0b433d8d8cbc0d183b106a3c60ce5c17e0777572.

Server

Desktop window

• The Settings page of quicktui-server gui now shows the path of tmux, Herdr, Luvus and Herdr Core that the server will use, also when you did not set one. A path the server found by itself has an Auto tag beside it; a path you set has none. A program that cannot be found shows Not found, and a row without a path shows Searching… until the search ends. Use Default now also removes tmux_bin_auto, herdr_bin_auto, luvus_bin_auto or hc_bin_auto, and a path saved with Change is kept as yours even when it is the path the server found. Before, these rows showed only Find automatically when the config file had no path, so you could not tell whether the program was found.
• The Status page of quicktui-server gui now shows No Session Backend Available when none of the enabled session backends is installed, also when this computer has another backend that is not enabled. Before, for example, a Windows computer with Herdr enabled but not installed showed no notice when Luvus or herdr-core was installed, while the Diagnostics page reported the missing Herdr.
• On macOS, the menu bar of quicktui-server gui no longer has a View menu or a File menu. The View menu held Toggle Developer Tools, which opened a UI inspector, and Reload and zoom items that did nothing in this window. macOS and Windows release builds also turn that inspector off.

macOS

• installer setup can now set up the notarized macOS app: when the installer passes the server inside QuickTUI Server.app, the service runs that executable and nothing is copied to ~/.local/bin. ~/.local/bin/quicktui-server becomes a link to the app's server, replacing a plain server that q.sh installed there before, and the ~/Applications launcher of earlier installs is removed. server_follows_app is set to false, so the server keeps running when the window closes; a value you already chose in the app stays.
• service uninstall and a plain-server install no longer replace or delete a QuickTUI Server app that sits at ~/Applications/QuickTUI Server.app; they change only the launcher that earlier installs wrote there.

Session backends and agents

• The server now finds the hc (herdr-core) and Luvus binaries the way it finds Herdr. QUICKTUI_HC_BIN and QUICKTUI_LUVUS_BIN in the server's environment now take precedence over hc_bin and luvus_bin in config.toml. When the configured path no longer works, the server searches again instead of failing; it searches the PATH of the service, of your login shell, and common install folders (for Luvus: ~/.local/bin, ~/.cargo/bin, /opt/homebrew/bin and /usr/local/bin; on Windows only PATH). A path the server finds is saved to hc_bin or luvus_bin, with hc_bin_auto or luvus_bin_auto beside it so that a refresh from the app can replace it later; a path you set yourself is kept. quicktui-server doctor now lists the Luvus binary under Session backends. Before, the server never saved hc_bin and stopped using hc when hc_bin pointed to a missing file, and it found Luvus only on the server's own PATH.
• The Agent session list in the app no longer shows Couldn't load sessions on a computer where Codex was never used, and the app connection no longer drops every few seconds there. Before, a missing ~/.codex folder broke the session list and live updates for every agent, for example for a user who uses only dsh. A Claude projects folder that the server cannot read no longer breaks them either, and Codex now shows as not installed instead of as an error when it was never used. server2-20260926-01 through server2-20261104-01 had this problem.
• The Agent session list now stays available when one agent's local data is broken. A Codex database that is locked, changed by a Codex upgrade while the server runs, or that holds a session row the server cannot read now leaves out only those Codex sessions, and the next read opens the database again. A session started in a folder whose name holds a tab, a line break, or more than 256 bytes now shows without a workspace name instead of failing the whole list. Before, any of these made the list show Couldn't load sessions for every agent.
• Live updates in the app no longer stop for every agent when one agent's data cannot be read, or when the first read after the server starts fails; that agent or session shows as unavailable and updates again once it can be read. One agent that answers slowly no longer delays the live updates and the status page rows of the other agents.
• A bug in how the server reads one agent's local data no longer stops the server, and one agent whose files hang (for example on a stuck network folder, or a Codex database replaced by a special file) no longer makes the session list, the status page, or live updates wait for it. The Agent session list now answers within its usual time and shows that agent's sessions without their status or last message until it responds again; the last messages of the other agents still show.
• One agent session the server cannot read now affects only that session. Before, it closed the app's whole connection every few seconds, which also dropped open terminals; stopped Agent push notifications for every session; or answered the session list with 403 or 404. The server now retries that session's live updates in the background and keeps everything else running. Tab titles of agent sessions again update within about two seconds after a change; before, they waited for the 15-second refresh. When the agent hook setup at server start does not finish within two minutes, for example on a hung network folder, the server now reports it and still shuts down at once.

doctor and CLI

• When quicktui-server doctor warns codex: the QuickTUI hook is waiting for you to trust it, its steps now say that the warning clears only after a new Codex session sends a message, and that trusting the hook in /hooks alone does not clear it. The steps also ask you to keep every QuickTUI entry enabled there.
• qsh web: when the connection to the server is lost while a browser terminal tab is still connecting, that tab now closes with code 1012 and the reason for the loss, as the tabs already open do. Before, it could close with code 1001 and qsh web is shutting down.

Install with:

curl -fsSL https://quicktui.ai/q.sh | sh -s -- install --channel server2

This command resolves the server from the live server2 channel in server-manifest.json; it is not a tag-pinned historical install.

Assets use these names:

quicktui-server-<platform>-<arch>
quicktui-server-windows-<arch>.exe
quicktui-server-<platform>-<arch>.sha256
quicktui-server-<platform>-<arch>.gz
quicktui-server-<platform>-<arch>.gz.sha256

Installer assets are not included in this server release. q.sh and installer assets are published independently from server2 releases.