Workspace chat

Ask questions across your whole workspace, get cited answers, take actions through confirmation cards, and share threads with your team.

Chat lets you ask questions across everything in a workspace: initiatives, documents, context items, goals, and uploaded files. It retrieves the relevant material, answers from it, and cites what it used.

Open chat from the chat panel in the dashboard. You can scope a thread to one initiative or keep it across the whole workspace.

Cited answers

Chat answers are grounded in your own content. When it pulls from a document, a context item, an upload, or a goal, it adds a citation marker so you can see exactly where an answer came from and open the source.

Citations are skipped inside code blocks, so a [1] in a code sample is never mistaken for a reference.

Taking actions in chat

Chat can do more than answer. When you ask it to create something, it proposes the action as a confirmation card instead of silently writing to your workspace. Four actions are available:

  • Create initiative spins up a new initiative.
  • Save as context item captures something as a labeled context item.
  • Create goal adds a goal to an initiative or the workspace.
  • Create document draft creates a document of the type you asked for, ready for you to open and generate.

Each card shows the details before anything is saved. Review them, adjust if needed, then confirm. Nothing is written until you confirm.

These same four actions are available to outside agents through the MCP server.

Threads

Each conversation is a thread. Threads persist, so you can come back to a line of questioning later. Start a new thread when you switch topics, and pick the scope (a specific initiative or the whole workspace) so retrieval pulls from the right place.

Sharing a thread

You can share a thread with the rest of a team or client workspace so colleagues see the same conversation.

When you view a thread someone else shared into a workspace, you can read it but the composer is disabled, with a short note explaining why. Only the thread's owner can keep sending messages in a shared thread. This avoids one person's view colliding with another's.

Where to go next