0.58.0

Released 2026-11-04.

Upgrading

• Reload every pi session after the update (/reload). The first pi session that loads 0.58.0 restarts an older sb server, and an open browser page reloads once on the new server’s hello.
• Nothing new appears in Herdr until you write to the head tower. With towerRuns off there is no head tower and every channel says so.
• The first-workspace mark is gone. Until now “head tower” meant the tower of the first workspace in Herdr’s order, and that tower carried a crown and head=yes. No workspace tower carries either now, and the head tower is now <workspace> digest line is replaced by head tower opened and head tower closed.
• A pi session on an older build keeps its resident tower and keeps working; it does not know head: true answers, so an older tower cannot answer the head tower.

The head tower

A tower of its own, in no project, that you talk to and that forwards your work to the towers that own it. The design is docs/specs/2026-11-04-head-tower.md; how it works is The head tower.

• One long conversation. Every run of the head tower resumes the same pi session, whether your message or a tower’s answer woke it. A session past 8 MB, or New conversation, starts a new chapter with a short brief of the last one, and the history pages across chapters.
• Forwarding. Its tower_send goes to one workspace’s tower (an id or an exact label), opening the tower first when there is none, and opens an ask H<n> that stays open for 24 hours. The workspace tower answers with tower_send({ head: true, inReplyTo }); the head tells you in a line.
• A narrow door. It listens only to you (the GUI, /boss head, the standing pane) and to answers to its own asks. A broadcast, a main’s message, or an answer with no open ask gets a receipt and wakes nothing. Its tools are tower_list, board_read, tower_send, tower_memory, tower_done, boss_server, and the read-only file tools: no shell, no mains, no Straw Link.
• Its workspace. Made on first use as 主塔台 or Head tower, its tab labelled with a crown, sorted first. Closing its tab, or /boss head close, ends the service; the conversation, memory, and asks stay and the next message resumes.
• Standard. A page of its own (/head) with the asks as chips and Close the head tower in the conversation box’s ⋯ menu, a crown button in the header (a dot, never a number, for a reply you have not seen), a crowned head node on the map that is the hub of its wires, and the first row of the phone drawer.
• Zen. Under the breathing circle, the head’s last lines (the boss’s in ash on the right, its replies in paper on the left) fade with age, from clear after 20 seconds to almost gone after three minutes; hover, focus, or a tap reads them clear. The input is a hairline until a click or Enter unfolds it. H, a wheel gesture up, or a swipe up opens the whole conversation, where a forward reads as one quiet line (“Sent to the Harbor API tower”). Items still take the screen first.
• pi. /boss head [status | leave | new | close | <message>] and /boss memory -w head.
• Header. head=yes marks the head tower alone; its forwards carry ask=H<n> and, when your own message started the turn, relay=boss:<event id>; a tower’s answer carries in-reply-to=H<n>.

Going back

Close the crown workspace by hand (or /boss head close). Nothing else changes in the workspace towers, and the head’s files are kept in <state dir>/head/.

A tower’s wait for you

• A question a tower records on you in its memory (a wait) now reaches you as an alert: one dialog with Handle, Later and Dismiss (zh-TW 去處理／稍後／略過), an item in Zen with quiet text buttons, the tab icon’s count, and a notification. It fires once per wait.
• Each wait line on the map says how long it has stood, with Handle and Dismiss. Dismiss drops it through the memory route (same CSRF and route checks as the other memory operations; paired devices only, never a Straw Link ally), and the tower does not record it again from an old handoff note.

Linux

• Restored subagents resume. After a Herdr restart or a reboot, a subagent pane on Linux is matched by the same rule as a run start (a process named pi that is the pane’s only pi or its process-group leader); anything less certain stays unknown and is not resumed.
• Reap takes no stranger. When a run’s recorded pi fails verification, nothing is signalled by name. A pi found by name alone is stopped only when the run never recorded a pid and a process table that was read shows it; two pi with no leader are never guessed.
• A pi under a wrapper is found in the pane and in reap.