Bot
A persistent teammate with a name, a role, and boundaries. It has its own 1:1 session and profile, and it does not disappear when a task ends. When it hits an obstacle, it first investigates on its own, tries the means available, and verifies against the original goal; it does not hand technical work it can finish itself to the user, and asks for help only with permissions, credentials, information, or decisions that only the user has. Trying things on its own is still bound by approvals, denials, Stop, and the boundaries of its profile, and it does not blindly repeat actions that have side effects. It says only what matters: a sentence whose removal or addition changes nothing in what it means to convey is filler, and it leaves it out (opening acknowledgements, restating the request, self-praise, sign-offs, ending by asking you to confirm or to say if anything should change); long content you asked for is written in full.
Avoid: Agent, child agent, subagent, assistant, Endpoint, "Got it!", "So sorry", "Thanks for the correction", "Let me know if you need anything"
Bot template
A ready draft of a teammate for one of the built-in engines: a name, duties and boundaries, drawn from the Bots used most so far, the boundaries carrying what the records taught (the Video Director hands over and waits for you rather than booking check-backs to ask your view; the Translator gives the translation in its reply; the Reviewer speaks only when asked) (ADR 0085). General has Assistant, Translator and Researcher; Video has Video Director, Story Writer, Subtitle Editor and Reviewer; Coding has Developer, Frontend Engineer, Backend Engineer and Designer. Only a start: each can be changed before it is made, and once made it is an ordinary Bot with no tie to its template. On first launch with an empty roster the wizard's last step picks a way of working (an engine) and makes the templates ticked; the new-Bot sheet offers them too.
Avoid: changing Bots already made when a template changes, a template choosing a Bot's model, first launch changing Settings' default engine
Roster
The set of all Bots on this machine. There is no limit on how many there are, and anyone can create one. A Bot is not a security boundary. In the app, the roster is a single row of letter tiles at the top of the sidebar, not a grid of cards, and it does not include you.
Avoid: team account, tenant, seat, roster cards, putting you in the roster row
User
The one person running this Mac. There are no multiple users and no share links. You are in every group; you and any Bot in a group can bring others in and remove them. Removing a Bot does not delete it. You appear in sessions, transcripts and the present members, but not on the roster's row of letter tiles.
Avoid: member, tenant, organization, Bot-only group without you, you in the roster
Profile
A Bot's name, role description, boundaries and avatar. A Bot can change its own name, role, boundaries and avatar, and no profile-change line is inserted into the transcript when it does; you can change them again at any time. Names of Bots that are not deleted must be unique. The avatar is a generated image or a raster image, not memory; a new Bot starts as one of the task map's characters, chosen by its name, which also varies its face and the way it faces: Pudding (the mustard teammate from the Deskfolk mark, with its antenna), taro (headphones, clipboard), sakura (beret, palette and brush), matcha (chef's hat, whisk), caramel (hard hat, hammer), sesame (glasses, pencil, book) or blueberry (wizard's hat, wand); Mochi's white is yours. Bots seldom share one, and a Bot is the same character on the task map; it acts out the Bot's status in the conversation list. Changes in the Bot panel save automatically (they are written once you pause for a moment, and anything unsaved is sent before you switch or close the panel); there are no save or close buttons, and the panel has only a single ✕ in the top-right corner. In settings, the workspace, endpoints, and MCP names / notes are likewise written as soon as you change them; adding an MCP server or changing its command / args / URL / headers still needs confirmation. A Bot's permission mode is set in its panel too, by you alone.
Avoid: writing memory into the profile, a save button on the profile panel, a save button in settings
Archive
Removes a Bot from the roster's main list; its sessions, profile and routines remain, and it can be restored. Its direct moves to the archived list, and what waits there does not count toward the Dock badge until the Bot is restored. Only deleting removes the Bot from the roster (files in the shared workspace are left untouched).
Avoid: hide as pause (archiving is not Stop)