Conversations & attachments
A conversation with a clear purpose.
Keep your request, responses and supporting material together.
A conversation with a clear purpose.
For a new task in an existing project or a follow-up to earlier work.
Putting every request in one long conversation makes previous decisions hard to find. Separate conversations give each piece of work its own instructions, route and progress.
Choose the provider and model at the start, then continue using the existing controls to change them later. Follow-up messages can be queued or used to steer the current task.
Take a closer look.
Explore the actual screens and controls. Click an image to see every detail.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Choose an available AI connection and model when creating the conversation.
- 02
Describe the result you want and attach relevant files. You can send follow-ups in the same conversation.
- 03
Reopen a saved conversation to review earlier requests and recorded activities.
How it could work for you.
Keep homepage design in one conversation and a navigation review in another, both under the same project.
How to assess the result
Conversation history is not a second copy of the project files. Check the project location before asking for changes.
Where to find it.
Project → New conversation; then the message composer
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 task progress are stored locally. Online conversation copies are included in Complete.
What you need to know
An attachment provides context. It does not automatically become part of the deliverable; ask for that explicitly when needed.