Chat

Chat is the human collaboration surface for the active workspace. It is separate from Otto: ordinary Chat never lists AI assistant sessions, and creating an Otto session does not create a human channel.

Conversations

Use the workspace conversation for shared discussion, create a group conversation with selected workspace members, or start a direct conversation. Group owners can manage members. Messages support replies, edits, deletion, emoji reactions, unread state, and live typing/presence when realtime is connected. Offline status means live updates are unavailable; it does not make a failed send succeed.

Access follows workspace membership and conversation membership. Sharing a conversation link or resource URL never grants the recipient access they do not already have.

Attach project context

The composer can attach:

• a workflow selected from a project in the workspace;
• a work item selected from a Task Space;
• a workspace or project Design Doc.

Attachments are durable links inside the message, not copies of the resource. The Shared links tab collects unique attachments from the loaded conversation history. Opening one rechecks current access, so removing project, task, or document access can make an older card unavailable.

Tasks can also use Share to chat to send their own permalink. A workflow or document remains owned by its original project or Design Docs authority after it is shared.

Keep secrets out of Chat

Messages and assistant prompts are collaboration records, not secret storage. Never paste variable values, API keys, access-token setup commands, or provider credentials into a conversation. Add a credential through Variables or the relevant connection UI instead.

Chat requires the collaboration capability in a hosted workspace. Local project editing can remain available when Chat is unavailable.