When a teammate shares a conversation with you, you see it in read-only view: you can read the messages but not reply. To pick up where it left off, you can fork the conversation. A fork creates a new conversation in your own list that keeps the original messages as context.
Fork a conversation
Open the shared conversation.
In the read-only banner at the bottom, click Continue in my chat.
Aracor creates the fork and opens it. You can reply right away.
What gets carried over
Original messages. The shared conversation's messages appear dimmed above your own, with a label like "Forked from [owner]'s conversation". They stay visible for context but are not editable.
Selected documents and folders. Any documents, folders, or synced folders the original conversation was scoped to are copied across, so the fork starts with the same context.
What's new in your fork
The fork is yours. You're the owner.
It uses the project's default visibility, usually Only you. Open the share menu to widen access. See Share a conversation.
The fork is titled Fork of: [original title]. Edit the title from the conversation header.
The original conversation is unaffected. Forking does not change anyone else's view.
When forking is useful
A teammate sent you findings and you want to keep digging without bothering them.
You want to take a shared conversation in a different direction without losing the original context.
You're picking up a deal someone else started.
People outside your workspace (guests) cannot fork shared conversations. They have read-only access only.