Chat Sessions

A chat session is a conversation with an agent that persists on the platform. Unlike a one-off request, a session keeps its full message history, has a name you choose, and can be picked up again later where you left off. Sessions live under Chats in the product navigation.

Resuming a session

Because sessions are persistent and nameable, you can leave one and return to it without losing context. Open Chats, find the session by name, and continue the conversation where it left off. The agent reads the prior messages, so you do not have to restate what you already covered.

This matters most for work that spans more than one sitting: a debugging thread, a review that waits on someone else, or a conversation you want a teammate to continue after you.

Linking sessions to tasks

A session can be linked to a task in the brain. Linking gives you traceability: the conversation that produced a decision or a change is attached to the task it belongs to, so anyone reading the task can find the reasoning behind it. Attachments from a chat can also be filed onto the linked task.

Link a session when the conversation is part of tracked work. That keeps the discussion, the deliverable, and the task history in one place instead of scattered across separate chats.

Customer-facing vs internal context

Each session carries a context toggle: customer-facing or internal. Use it to signal how the conversation should be treated. A customer-facing session is meant for content that a customer may see; an internal session is for private, team-only discussion. Set the toggle to match the audience before you start sharing.

Related