Download

Only this machine's own pages can change it. A page on another site could open a terminal connection or send a request that changes something (close a session, write a setting) while you were signed in to your machine's web terminal in the same browser. st now refuses every request that changes something, and every terminal connection, unless it comes from the machine's own page or from an app. The desktop and phone apps are unaffected. Reading is unchanged.

One owner check for everything. Every service that changes something asks the same owner check, so a future read-only link is refused by all of them at once.

Files for the desktop. The desktop can browse folders and preview files on this machine, or on another of your machines through its existing connection. It can save a text file it opened: an existing UTF-8 file of up to 1 MiB, only if the file on disk is still the one that was read. A file changed since is refused and nothing is written. The new file replaces the old one in a single step, keeping its mode. Secret files stay protected by the machine's existing setting.

Decision gates in any terminal. st gate list, show, answer and cancel work outside tmux, through this machine's running st. A gate can be answered from the desktop or the phone.

CI across the repository. The CI board shows the repository's latest 50 GitHub Actions runs, on every branch and tag, with each run's branch or tag. A workflow with no run in that window says "No recent run".

A Pro account's machine takes sophonz's relay without a token to type. Its heartbeat asks for one, and the account answers with the machine's own relay. st tries it once and moves the share onto it. The machine's address then stays the same across restarts, instead of a new quick-tunnel address each start.

• What you chose wins. A Cloudflare quick tunnel or the tailnet picked with st route, or a relay of your own set with st relay set, keeps the managed relay unused. st route relay picks it. st relay reset chooses a quick tunnel and stays there, even before the relay arrives.
• A relay that is the same as before is neither tried again nor reconnected to. A new one that does not take the machine leaves the share as it is, and it is tried again with the next report.
• When the plan ends, st goes back to a quick tunnel at once. A machine taken off the account signs out and stops sharing, as before. The relay is the account's: signed out, or signed in as someone else, st does not use it.
• If the relay refuses the machine when st starts, the share runs on a quick tunnel until the next report says what is true now. st route says so, and why.
• st route and st relay show the relay as sophonz's, from your Pro plan. The relay's token is never shown or logged.
• /api/version says relayAuto: 1. An app that sees a Pro account without it can ask you to upgrade st.

opencode 2. st's opencode plugin loads in opencode 2, which refused the old one with "Plugin must export a default definition…", and opencode 1.3.4 and later keep working with the same file. st hooks install turns off opencode 2's shared background service so that each opencode window is its own pane. st starts opencode with --standalone where it starts it. Without that, every window's turns showed under the first one. st hooks shows the old plugin as outdated, and automatic updates rewrite it.

Codex. st hooks install turns off Codex's shared app-server, and st starts Codex with --no-daemon, so that each Codex window is its own pane. A session still on the shared app-server is not given another window's turns. A Codex whose sandbox keeps its shell from st runs st's commands through one MCP tool, st. A shell that cannot reach st says so. A Codex approval prompt is read the same at any window width, so an answer from the phone goes through.

The web terminal. A page left open past its sign-in says the sign-in expired. It offers to open this machine again or go to the dashboard, above the token field. A split window has a Compose button in the active pane's corner, and none in a pane too small for it. The machine's links sit inside its block in the sidebar. A Codex pane finds its conversation again after st restarts.

The vault page. A notification about a brief opens it, with its .briefs folder in the tree.

st serves the vault page. A machine's documents open as a vault: a file tree, notes in Live, Read or Source, the graph, and the vault's own plugins. Every screen opens the same page from st, at /vault on the machine's link: the desktop app, the phone apps, the web terminal and any browser. ?scope=<session> or ?scope=<session>/<window> opens one session's or window's folder as the vault's root. An edit shows on every other device that has the note open within a fraction of a second, through a share's tunnel too, and a file an agent writes arrives within the 2-second scan. Two devices saving at once do not write over each other.

• Live edits with the formatting shown, Read is the reading view and Source is the markdown as it is. The switch sits in the note's header; ⌘E toggles Read.
• Tables are edited where they are: click a cell, Tab and Enter move, a right-click adds, moves and deletes rows and columns. A table wider than the page scrolls in its own box.
• Callouts are drawn and fold, and $…$, $$…$$ and fenced math are typeset.
• ⌘G opens the graph of the whole vault, and the local graph shows the note in front with its neighbours.
• Settings › Appearance sets the body width and turns CSS snippets on and off; a note's cssclasses apply.
• Plugins are your own: put one in the vault's plugins folder and turn it on in Settings › Community plugins. Plugins run in a sandbox with none of st's cookies or tokens. st's docs show how to make one, with a working example.
• On a phone the page has a phone layout: drawers for the sidebars, a bottom bar, an editing toolbar above the keyboard. It opens on a note, with the folders it is in on a line under the title.
• The page shows a progress bar from the first moment, and through a tunnel the first note appears in under a second once cached.
• A document notification opens that note.
• Folders whose names start with a dot stay hidden. st's .briefs folders can be shown from Settings › Files and links, a choice kept per machine.

A note made in the vault is a document. st keeps its id in .st/ rather than in the note, so it is in st doc ls and on the phones. st doc --folder critic puts the document in critic/ on disk. GET /api/docs says which session or window folder each document is in (vaultFolder). /api/version says docs: 5, vault: 1 and vaultReady.

st ui shows this machine in one terminal screen. It starts on a tree of your machines, sessions and windows, this machine first, and lists windows, panes, the coding agents in them, orchestration runs, CI, the vault's notes, plan usage and the machine's CPU, memory and swap, refreshed every two seconds. enter or a attaches, on another machine too; from inside tmux 3.3 or later it opens in a popup and Ctrl-b d comes back. o adopts the selected agent as a worker and R releases one, each after y. c opens a window's newest GitHub Actions run. : runs any st command. The header shows the sophonz wordmark and each weekly limit by name (weekly sonnet, weekly opus).

Agents. A working agent is teal in st ui and the web terminal, apart from the orange of an agent that asks for you. A program that reports its own status (OSC 7501) is believed, and st ui marks that state as reported. st worker wait --check-in comes back with how the workers are and leaves them running. st --skill prints the agent's guide in one read. A send another machine turns down says why. st plugin install, and st after an upgrade, update Claude Code's copy of the plugin and the Codex skills where they were installed.

The web terminal. The machine row's Doc opens the vault in a tab, and a session or window row has a Doc button for its folder. The built-in sophonz and Light themes take the desktop app's colours, every theme paints the page around the terminal, and the selected session, window, chart row and document are cyan in sophonz and Light so they read clearly.

"This machine" means st's token, not the loopback address. A page in a browser on the same machine connects from loopback too, so st doc's origin claims, st hook and st gate ask are trusted only with st's own token, which st's programs always send.

Release candidates. st upgrade --channel rc follows release candidates and st upgrade --channel stable follows releases. The choice is kept on the machine, and /api/upgrade and /api/version say which channel is in use. An st on a candidate is not taken back down; this release arrives on top of it.

st doc <file> --folder critic now puts the document in the vault's critic/ folder. Until now it said "in critic/" and left the file in the folder of the window it was written from: --folder set the label the apps sort by, and only a settled decision gate's record was placed in critic/ on disk. So a decision a coordinator filed there was in critic in st doc ls and the apps, but not in critic/ when you opened the vault. Now the file goes to critic/<name>.md at the top of the vault.

A document filed that way before this release is still where it was written. st doc mv <id> critic takes it to critic/, and moving it to another folder later brings it back to its window. The move is made by the st that is running, so run it once that st is this version.

critic has no folders inside it. A decision is not a session's or a window's, so there is nothing to sort it by below critic: --folder critic/sub, st doc mv <id> critic/sub and st doc mkdir critic/sub are refused, and so is renaming or moving critic itself.

What did not change: the document keeps its source, so one you wrote with st doc still says it came from cli. Everything not filed in critic stays where it was, in its session and window folder, with briefs in that window's hidden .briefs/, and a file you moved yourself in the vault is not moved back.

Two things said something was wrong when nothing was.

An update st turns down on purpose now says so. There are six reasons st will not replace itself -- it is a development build, it is the copy inside the desktop app, Homebrew owns the file, it is a kept earlier version it fell back to, the machine is signed out and its tunnel address is the only way in, or ST_VERSION pins it -- and each one hands you the thing to do instead. None of them is a breakage, but an update had only done and failed to end in, so all six arrived as failed and the instruction beside them read like an error. The status now carries why when st turned the update down, and leaves it off when an update was really tried and broke. The desktop app, iPhone and Android read that and stop calling it a failure: each says it cannot update from there, in its own words, and shows st's own sentence under it. That sentence has not changed. An st from before this field sends no why either way, so a missing one is also what an older machine's refusal looks like.

A worker's st worker done is no longer dropped as late. st worker send wrote down the time after the keys went in, and the send answers only once it has watched the prompt arrive, which takes up to 1.6 s. An agent that submitted faster than that looked like it had taken the prompt before the work was sent, so its report was written and not counted. That left the pane's @st-done unset, which is what st worker wait reads, so finished work stayed unfinished and a coordinator waiting on it never came back. The time is now taken before the keys go in. On a busy machine it hit four times in one session.

st doc migrate gave you a vault, but it gave you all of it: 591 documents in one list, 583 of them briefs sent between agents. The ones you wrote were lost among them.

Briefs move into the window's hidden .briefs/. A vault app does not index a dot folder, so what it shows you now is the documents you and your agents meant to keep -- eight, where it showed 591. st doc ls and the apps still list the briefs; nothing was deleted and no file changed a byte. The pane folder is gone with them: a document sits at <session>/<window>/, because a pane is where an agent happened to be sitting, not what the document is about.

Every decision gate is kept as a document in critic/. The question, every option with the one that was chosen, the written answer, when it was asked and answered, and which session, window and pane asked it. st gate list forgets the oldest past 200; the folder does not, and a gate that has not been written yet is not forgotten. That folder is what the next agent picks the work up from, so ask a decision through a gate and write the question to stand on its own.

The layout move has no undo. st doc migrate --undo still does what it always did -- it takes every document out of the vault, back to ~/.sophonz/docs -- but it will not put the pane folders back. Copy ~/.sophonz/vault/machine before you run the migration if you want a way back; the move writes what it did to .st/relayout-<time>.json either way.

prompt-opened now says gate in the clear, true for a decision gate and false for every other prompt, so a phone can be told to alert on decisions only and stay quiet for the rest. What the gate asks stays sealed.