A branch's worker registers again, as it starts, what its journal says the branch still asks, budget questions included; /new --branch forks the activated branch or says which it needs; a conflicted merge says it was aborted; a window that goes leaves the focus; a branch's row names its model, a dismissed one is titled by its first prompt, and a subagent by its own agent¶
TUI decision 158 · accepted · 2026-10-11 · issue #502
- An approval asked before a branch's worker restarted. The parent's screen answers a
branch's approval through
Client.Daemon.call_target/2, which finds the branch by a{:call, parent, call_id}registration the branch's worker made as the request went by. It died with the worker: a crash and the supervisor's restart, or the session left and opened again (reopen_branches/1), and the new worker resumes its subscription past the request, soywent to the parent's own session and the branch waited for ever. Re-registered, not routed by the event's session: a worker that starts as a branch (as:set) reads its journal once and registers every call still asked, an ask with no answer after it. The answer stays one lookup, the cost falls where the journal is already read whole (opening a session rebuilds the screen from every branch's journal), and no screen or approval box changes. Routing by the event would have meant carrying the branch's own session id on the event the parent's screen gets and through the approval box, which another slot owns, or reading every branch's journal at each answer. The budget question (budget_ask_started) was never registered at all, so a branch's went to the parent's session even without a restart: it is one of the asks now. /new --branchin command mode forks the branch whose window is activated (typed in its box, or the palette's/newtaken into it), its own session throughsession.fork(root Decision 812); the session itself from its own window, on a pod, or when its own agent has work and is listed (atroupe run). With no window activated and the work in the branches it forks nothing and says which window to open (open its window (1 build-1) and type it there), or that no branch has started. Not chosen: a--branch <window>argument, which would change the command table's row and its generated help for what the window's own box already does.- A merge that conflicted was aborted by the daemon and the checkout left as it was
(Decision 647), so "resolve in your checkout" sent the person to resolve nothing. The
notice says the merge was aborted and the checkout is as it was, to merge the branch by
hand, then
/discardthe window; the window and its worktree stay. The window's own line says the same. - A window that goes while it is activated (
/merge,/discard,/dismisspicked from the palette over it, a cancel at rest) returns the screen to the command line when itswindow_dismissedarrives, rather than leaving a focus that names it until the next key. - A branch's row names the model it runs, as its own agent's replies name it
(
llm_response'smodel, resolved:quick's is the cheap one), in the row's muted figures before its tokens and cost; nothing before its first reply. Not chosen: the agent file's alias fromagents.list(cheap), which the screen does not hold in command mode and which is not the model. - A dismissed branch's picker row is titled
build-1, dismissed: <first line of its prompt>, its first input when it was opened with none, rather than the daemon's title for its session, which is the worktree it worked in. - A subagent is labelled with its own agent in the window's side panel and the
observer (
explore#1 (explore), not the window'sbuild):agent_named, which a subagent'sagent_startedbrings, names that agent; the window's own agent's name follows it too, as its header already did.
Governs: clients/tui/lib/troupe/remote/worker.ex, clients/tui/lib/troupe/client/daemon.ex, clients/tui/lib/troupe/client.ex, clients/tui/lib/troupe/ui/tui/server.ex, clients/tui/lib/troupe/ui/tui/model.ex, clients/tui/lib/troupe/ui/tui/view.ex