Roles
The three long-lived roles you talk to, what a role's screen shows, its sessions and seats, and what the console does not do there.
The fleet has three long-lived roles you talk to, under Talk to (Advanced: Roles) in the sidebar:
| role | what it does |
|---|---|
| Advisor | thinks with you, challenges the direction, finds the next useful question |
| Master | coordinates the work — dispatches legs, reviews, lands wagons — and keeps the fleet moving |
| Scribe | keeps the record coherent and turns decisions into durable documents |
A role runs as a session of an agent CLI on a seat — an account on a machine of the fleet. Which agent backends exist, and what each one is proven to do, is on Supported agents. Which seat each role works from is chosen in Settings → Seats → Cast roles, and can be changed there later. Every session is a row; every turn is in its transcript.
A role's screen
One pane, reading from the top: the session bar, the conversation, and the composer.
The session bar names the open conversation (click the name to rename it) and its state — live, working, waiting for you, closed, failed. Its acts are Restart, Close session, Pin to dock (keeps the conversation in the bottom panel) and + New session. On the Master's screen it also leads to Legs in flight, the legs that master has running now.
The arrow beside the name drops the sessions panel over the conversation: every session of this role — live first, then closed — as tiles or a list, with search. A session can be removed from the list or deleted from every list; deleting keeps the conversation's files.
A new session asks which seat to start on. The picker shows each seat that allows this role, its vendor account, and how much of its usage window is spent — or that the allowance has not been read. A seat holds at most 20 live sessions; close one to open another.
The conversation
- Your turns show delivery state — sending…, delivered ✓, not delivered, or outcome unknown.
- The role's turns show its thinking, the tools it used — grouped and folded, each with what it did (Read, Edited, Ran, Searched …), how long it took and whether it failed — its answer, and a cost line with its billing class.
- A relay card appears when a role wants to hand something on: the text, with Forward or Copy.
- A rotation bar appears when the fleet advises rotating the role, with the reason.
- Notes in the stream say what the console saw and did not expect: events that were not received, a usage limit the vendor reported, a session that closed or failed.
The composer. Write and press Enter to send (Shift-Enter for a new line, or choose Cmd-Enter to send in Settings → You). You do not choose a model here — the model is a fact of the seat the session runs on, shown beside the send button. A prompt opened from the Prompts screen arrives in the composer unsent.
What the console does not do here
It does not run anything on your behalf, and it does not retry silently. A turn that did not reach the role says so, and what you wrote stays in the composer. A gap in the stream is marked as a gap. When a seat is signed out with its vendor, or its allowance is spent, the conversation says which and when it comes back — and points to another seat if the role has one.
A closed session is never reopened. Its transcript stays readable; where the bar offers Continue, it picks the conversation up with its history, and otherwise you start a new session. A conversation interrupted by a console restart continues from where it stopped, with its history, when you open it again.