Side conversations & model collaboration
Separate investigation from the main thread.
Split off a question so another model or conversation can contribute to the project.
Separate investigation from the main thread.
For a focused review, analysis or separate subtask.
Research or review can distract from the main implementation. Subchats give related work its own conversation and model while staying under the parent conversation.
Choose whether to share recent parent context. Each subchat has its own task state, but works in the same project folder.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Give the subtask a clear goal and choose an available route.
- 02
Use relevant context in the side conversation and follow its progress.
- 03
Bring findings back to the main conversation or continue the subtask separately.
How it could work for you.
Use a subchat to review wording while the main conversation manages the page structure.
How to assess the result
Shared files still need coordinated writes. A separate conversation is not a separate filesystem sandbox.
Where to find it.
Conversation → Open side conversation / subchat
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Conversations and their relationship stay attached to the project.
What you need to know
A side conversation is not an unrestricted parallel writer. Tasks in one project must account for shared files and execution locks.