shell.online 0.25.0

A security patch. Upgrade if you share sessions from a machine that runs other programs as you, such as coding agents, MCP servers or install scripts.
Security
- A session's browser password no longer sits in any process's environment. The machine daemon handed a browser-started session its password in SHELL_ONLINE_E2EE_PASSWORD, and every background session kept it there for its whole life. Any program running as the same user could read it (ps -E, /proc/<pid>/environ). It now goes between shell's own processes over a pipe. Setting SHELL_ONLINE_E2EE_PASSWORD yourself still works as before.
- The program a session shares no longer inherits the session's password, name, command or browser request. A shell run inside a browser-started session silently reused the parent's browser password and published the parent's command and name as its own, and shell password rotate run from inside rotated to the same password. The accounts service now also lets only one session claim a browser request.
Sessions that are already running keep their old environment until they restart. After upgrading, restart the machine daemon so browser-started sessions use the new handoff.

Removed

• The agent-record transcript added in 0.24.0 is withdrawn. It found a record by the directory the session started in, so sessions started from the same directory could resolve to the same file. The chat reads the screen again. …

The chat renderer now reads a coding agent's own record of the conversation instead of the screen it draws.
A full-screen agent repaints a grid, so what a viewer held was one screenful of a projection: history was gone, the contents changed with the terminal's scroll position, and whether the agent was working had to be inferred from a spinner that never says it has stopped. Claude Code and OpenClaw both keep a machine-readable record of the same conversation on the host, written per message and per tool step while a turn is still running. The CLI follows that and sends it as its own frame, sealed with the session's cipher, so the relay forwards it without being able to read it.
What travels is narrow: what was said, the name of a tool, and the questions an agent is waiting on. Thinking, tool inputs and attachments stay on the machine. A session that never runs an agent sends nothing.
Questions an agent asks are now answered in the chat. They arrive with their options, are drawn as buttons, and pressing one answers the program's own menu.
Also in this release: Shell Keep gets a larger field, a new HUD, training at the Forge and touch controls, with a fix for "Gather now" answering an internal error; and the stats dashboard shows how far new accounts get.
Upgrading is worthwhile for anyone using the chat renderer with an agent: the host side of that feature ships in this binary.
See the changelog for detail.

Terminal sessions started from the browser on macOS no longer run at background priority.
- On macOS, the launch agent now runs the daemon as an Interactive job, not a Background one. Sessions started from the browser inherit the daemon's limits. Under Background they got the lowest CPU priority and throttled disk reads, including reading swapped memory back in. On a Mac short of memory, an idle session could take 5–30 seconds to show a keystroke (#268).
- shell service status says when the installed launch agent still uses the old setting.
Upgrading a Mac: install this release, then run shell service install to rewrite the launch agent. This restarts the daemon, and the restart re-keys it. Running sessions are not closed. They keep background priority until they are restarted, while new ones start at normal priority. Linux is unchanged; its service never lowered priority.
Install or update with the documented installer, or download a binary and check it against SHA256SUMS. The build-from-source instructions pin this release.
Verified: all 15 required GitHub checks passed on #268 and on the release PR (#271), including Windows and emulated Linux architectures. The published /downloads/SHA256SUMS matches this bundle, and the macOS arm64 binary matches its release.json checksum. Release bundle: 78 files, including installers, checksums and metadata.
Builds on v0.23.2: terminals sized to the screen showing them.