What a workspace holds
Threads
Conversations between people and assistants, with read state per person, mentions (
@everybody notifies everyone in the thread) and replies.Assistants
Assistants of the account linked to the workspace, or created for it, each with its model, tools and instructions.
Knowledge and skills
Documents and skills the assistants of the workspace can read, plus every file its threads produce.
Rules and memory
Standing instructions for the whole workspace or a single thread, and the core memory each assistant always reads.
Automations
Work an assistant does on a schedule or when an event arrives from a connected app, posted to a thread.
Members and roles
Owner, manager, member and viewer. External members from other accounts can be invited to a single workspace.
Direct messages
Private conversations are account-wide: any two people of the account can write to each other, whatever workspaces they share. They have their own Direct messages section, next to the workspaces, and only the two participants can open them and their documents. A document from a private conversation can be published as a copy in a shared thread.How an assistant takes part
An assistant answers when someone addresses it, either by mentioning it or by replying to one of its messages. The workspace can also be set to suggest an assistant, or to bring one in automatically. While it works, the run is visible in the thread: thinking, writing, the tools it calls. Sometimes it waits for a person:- A question. The assistant asks with options or free text, and the run continues with the answer.
- An approval. Some tools, such as the terminal, need someone to approve them before they run.
waiting_input and waiting_approval, and
you can answer or approve them from there too.
Roles
A personal workspace belongs to one person and nobody else can see it.