The terminal can leave

Close the terminal and the run keeps going. Come back, and it is read from the top.

simulated

simulated

• One flow per directory, any number of chats. Another checkout of the same project is another directory, with a flow of its own; every chat is held beside the flow, and a chat nobody is reading folds away until you say something in it again.
• Leaving is not stopping. Exiting with a flow running asks: leave it going, or stop it for everybody.
• A reboot ends it. The run lives on its machine. A flow that can be picked up carries on from where it stood.
• Only from a real terminal. Piped, redirected or unattended runs end with their process.

Several people on one run

• Everyone is named. A frontend is a name and a kind, alice@tui or bob@sdk, and every answer, line and stop says who.
• Claims are about questions. Anybody may still say anything to any agent.
• Leaving hands your part back. A frontend that goes gives its roles back to anybody.
• Programs too. A program on the SDK is a frontend like any interface, and so is a browser on hmz web.

Stop itStopping a flow, and what it leaves behind.Pick it upCarrying on after the run itself has gone.How it is heldThe host, its frontends, claims, and doing it all from Python.