Skip to content
- A tower’s wait for you is answered where it shows, in every view. Zen’s 去處理 / Handle opens a hairline box under the question and never leaves Zen; Enter sends your words to the tower, Esc folds the box, and after the tower takes them the card leaves for the breathing circle. Standard and Geek answer the same way in the wait dialog and in the wait’s row on the tower card; the tower’s comms is a secondary link. All three views send through one shared path.
- “Answered” lives on the sb server. An answer marks the wait answered (
input with answers), so every view and every device shows Answered, waiting for the tower and no view alerts for it again; a wait that changes alerts again. A refused send marks nothing, and /quit or /new sent as an answer is refused (not_an_answer). An answer typed in the comms composer leaves the wait open. Answered waits no longer count toward a tower’s 12 open waits, and /boss memory says you answered them.
- Fixed on the way: Zen read the tower’s
{accepted: true} as a refusal and played the low bowl; the wait card’s title showed the unit twice; known refusals are now in your language.
- A run’s first start no longer hangs 30 s. The run waited for the tower prompt to say it was leaving, not for its process to exit, and
herdr agent start landed in zsh a few ms later with its Enter dropped. The start now waits for the prompt’s process to exit (2 s bound, named in the log if it does not) and 300 ms more. Windows is unchanged. A crashed start’s log line and run detail now begin with Herdr’s code and the start of its stderr.
- A tower can relay a device’s answer to a main of another workspace. In trial 8 a main of Agent Root called MP Center’s tower to brief a teammate’s device. The tower sent the brief, but only a main of its own workspace could be the requester, so the box’s report reached an ally run and stopped. The requester (and
tower_send’s for) may now be a live main of any workspace on this computer that sent this tower a call_tower expecting an answer in the run; the device’s answer then goes to that session by intercom. for naming a session that did not call the tower is refused outside the tower’s workspace, and a tower with no (or two) askers is still told no session is bound, which tower-run.md now tells it to pass on to the requester. Single use, 24 hours, device-bound, and revocation are unchanged. Only the computer whose tower sends needs 0.58.2; the receiving computer needs what 0.58.1 gave it.