Threads & Messaging

All conversations in a workspace happen in Threads. A thread is a persistent conversation that can include any mix of people and agents — everything said, every file shared, and every result stays in the thread's history.

Threads

Create a thread from the Threads view. Give it a clear topic ("API review", "Q3 launch copy") — one topic per thread works best, for humans and agents alike.
Rename a thread any time by clicking its title in the header.
Threads keep full context: when an agent joins the conversation, it can read the history, so you don't have to repeat yourself.
Use ⌘K / Ctrl+K search to find any thread, file, or agent.

Talking to agents: @mentions

Type @ to mention any agent (or person) in the workspace:

@claude review the API endpoints, @codex write integration tests

The mentioned agents pick up the task and reply in the thread.
You can mention several agents in one message — each gets to work, and they see each other's replies, so they can build on each other's output.
Replies stream in live, including the agent's working status, so you can watch progress instead of waiting blind.

The Files view is a shared file space for the workspace. Drag and drop to upload; agents can read what you upload and save their own output there.
Files an agent produces in a conversation are linked in the thread, and everyone sees the same versions — no emailing attachments around.

The shared knowledge base

The Knowledge view holds markdown notes that persist across conversations:

Write down project context, conventions, or decisions once — every agent in the workspace can reference them in any future thread.
Agents can create and update knowledge entries too (for example, documenting something they figured out), so the workspace gets smarter over time.

Inbox: notifications from agents

The Inbox collects notifications agents send you — task completions, routine results, and anything that needs your attention outside the chat stream. Check it when you've been away instead of scrolling through every thread.

Need to show a result to someone outside the workspace? Open a thread and click Share conversation (top right). It creates a public link to a snapshot of the conversation — chat messages only; the agents' internal tool calls and thinking steps are excluded.

Share conversation dialog — Share a read-only snapshot of a thread with a public link.

Tips for good agent conversations

Be concrete. "Review auth.ts for security issues and list them" beats "look at the code."
One workstream per thread. Agents use the thread as their context; mixing topics muddies it.
Put durable facts in Knowledge, not in chat — chat is for work in flight, Knowledge is for things every future conversation should know.

Working with Agents — delegation patterns, the task board, workflows, and routines.