Skip to content

/agents opens the one agent picker at the manager's density (subagents and files not read too, each row its mode, facts and what it stands in for) and /new opens it to start a session on the agent chosen; from any of them n makes a new agent from the one selected, and what the manager's page does to an agent comes back to the picker on what was saved, so Enter starts on it

TUI decision 166 · accepted · 2026-10-23 · issue #594

Issue #594's terminal rest, on TUI Decision 164's picker and root Decision 920's list. Amends TUI Decision 156 (/agents is no longer a page of its own) and 151 (/new asks for its agent first).

  • /agents is the picker at the manager's density. The same popup Ctrl-N and Tab open (AgentChooser), listing the subagents too (agents.list with subagents: true) and, after the agents, the files found and not read, each with why. Each row is the name, the agent in use marked, the four origin words, its mode, the facts the manager's list had (model, tool count, read-only, cap on turns), what it stands in for and the windows that run it; beside it the fields the manager's page showed (Agents.fields/2), why it cannot be changed here, and its instruction. It takes the room the page had, not the picker's. Enter reads the agent whole, as /agents' Enter did; b, s and e are the picker's, and c, x, v and r the manager's own.
  • The manager's page is the step an action needs, then the picker again. e, c, x, v and n open /agents' page on the agent for that one thing (the editor, the save question, the delete question, the whole instruction), and its end comes back: Esc with the selection kept, and a save or a delete with the listing read again, the cursor on what was saved and the picker's line saying what Enter (or b) now does to it. A save refused (the daemon's check, a file another client saved) stays on the page with the edit kept, as before; only a save that wrote leaves it. So making an agent and using it are one flow, the issue's save → start.
  • n makes a new agent from the one selected, in every picker: its file, whichever layer it is in (Troupe's own, the organisation's, a person's or the repository's), opened in the editor under the name typed, and saved like any new agent into the layer the person picks; unchanged, it is still saved, since a copy of an agent that works is what was asked for. The answer to the issue's question on templates: the shipped agents are the templates, copy-only, and no separate set is kept. Refused on a pod, where nothing is written, with the listing's sentence. /agents' page's own blank template stays where the page is.
  • /new takes its agent from the picker. /new and /new --private open it (title "a new session on"), and Enter, or b, makes the session with that agent as its profile; the new screen's first line starts that agent in the checkout, as a Ctrl-N choice does. Not for --branch, which keeps the agent of what it forks, --remote PROFILE, which names the plane's, or a pod's session on screen, whose listing is the pod's and not what a session here could run.
  • A subagent is never started or switched to from a picker: an agent hands work to one. The refusal says so, and that n makes a primary from it.

Governs: clients/tui/lib/troupe/ui/tui/agent_chooser.ex, clients/tui/lib/troupe/ui/tui/agents.ex, clients/tui/lib/troupe/ui/tui/server.ex, clients/tui/lib/troupe/ui/tui/view.ex, apps/troupe_core/lib/troupe/commands.ex