Multiple Conversations

Use separate conversations in one project to advance scripts, characters, visuals, and other relatively independent tasks.

Why use multiple conversations

As one conversation grows, different goals, revisions, and context can become mixed together. Multiple conversations let you separate discussions by creative task while continuing to share the same project documents, media, and edits.

What you can do

Create conversations for relatively independent tasks.
Switch between active conversations at the top of the project.
Rename conversation tabs to show what each discussion is for.
Close tabs you do not need now and reopen them from Conversation history.

Each conversation has its own message history, but all conversations still belong to the same project.

How to use it

Select + in the top bar of the chat area on the right side of the project.
Enter the new task for this conversation.
Select conversation tabs in the top bar to switch between conversations.
Double-click a conversation name to rename it. Close the tab when you no longer need it open.

Closing a tab does not delete the conversation. Open Conversation history when you want to return to it.

Tips

Keep follow-up changes for the same goal in the original conversation so the Agent can use earlier decisions and feedback.
Start a new conversation when the task is relatively independent, you want to explore another direction, or you want to rebuild the conversational context.
Names such as “Script structure”, “Character design”, and “First storyboard” are easier to recognize than default names.

Usage limitations

A new conversation does not automatically inherit messages from another conversation. Put collaboration rules that must persist across conversations in the project's AGENTS.md. Keep scripts, settings, and references in ordinary project documents and refer to them when needed.
Project content is shared by all conversations. Media or documents created in one conversation can also be found and referenced from another.
Creating a conversation separates the discussion; it does not copy the project or isolate its content.

Conversation history: reopen earlier or closed conversations.
Refer to project content: add explicit project context to the current message.
Permission modes: choose which Agent actions require your confirmation.