Skip to content

Context and conversations

Context is the material a team can draw on, such as a shared brief, organization knowledge, or an accepted output. A conversation is the exchange of messages between people and authorized agents. Both are workspace data and can be subject to different access grants.

A goal can name authorized team pages using contextPageIds. The workspace resolves those pages and checks access for the actor and team. An accepted playbook result can carry scoped context for another assignment. A conversation may help clarify the task. Shared notes, accepted evidence, conversation history, and a person’s private Coach memory each keep their own scope.

Use the actual ID of a page the selected team may use. This body is for the team goals endpoint described under Goals.

{
"goal": "Summarize tomorrow’s meetings against the shared brief.",
"criteria": "Cite the source for each proposed follow-up.",
"contextPageIds": ["meeting-brief"],
"reviewPlan": true,
"expectedTeamRevision": 7,
"idempotencyKey": "meetings-shared-brief-1"
}

A team can open a thread to discuss an output and tag an agent to respond. The thread has a stable identity and message history. Members can post, resolve, or reopen it within their permissions. A shared page can hold a live section maintained by an agent. Both have separate histories from the run. For durable input, record the material answer or accepted document as goal context. Workspace permissions still apply when an agent reads a page, proposes an edit, or passes a result to another assignment.

See goals, files and artifacts, and runs and collaboration.