Sessions

A session is one conversation with the terminal inside a deal. Closing the tab doesn't end it: work you started keeps going, and when you open the session again the whole conversation is there, right where you left it.

Start and resume sessions

Each deal has a conversation list. Start a new session blank, or from a quick-start: cards filtered by the deal's stage that pre-fill a common command.

Older sessions reopen from the conversation list or the session browser, which lists them with their age and length. Reopening one shows the full conversation.

The terminal names sessions and writes a one-line preview for each one, keeping the conversation list scannable.

Idle recap

After a few minutes of inactivity, a one-line recap appears above the composer: the goal, the current task, and the next action. It disappears after your next message.

Deal memory

Each deal has its own memory: facts, parties, decisions, and your feedback carry across sessions and teammates, so nobody re-explains the deal at the start of each conversation. The terminal adds to it quietly as it works.

There's no separate memory screen; you work with memory through the conversation:

• To see what it knows, ask: "what do you remember about this deal?"
• To save a fact deliberately, run /deal:remember.
• To fix something, say what's wrong and what's right, then ask it to repeat what it now remembers if you want to confirm the correction took.
• What belongs where: memory holds the deal's story and decisions; numbers and documents belong in files, where you can see and check them.

Deal memory is shared with everyone who has access to the deal.

Admins can also set firm context for the whole organization, which every session in every deal receives as background.

Update notices

When a notice says a new terminal version or updated commands are available, open a new session to pick them up. Existing sessions keep running on the terminal version they started with.

Next steps

• Commands: the / menu and the four command verbs.
• The composer: keyboard shortcuts, sending while the terminal works, and interrupting.
• Firm context: background for the whole organization, received by every session.