Conversations
Keep a task understandable as it develops across several messages.
Start a new task
Open a new conversation
Choose New conversation. Select Content or Work according to the task; for file work, confirm the project folder.
Check the model
Open the model selector and check its source and availability. A model listed in a menu is not necessarily ready to call.
Write the first message
Explain the desired result, material, and constraints. Add the information needed for this task instead of your entire archive.
Send and watch the state
Send once and wait for a response, permission request, or error. Review the visible state before trying again.
Use the notes below to draft a short introduction for a first-time reader. Keep the dates and numbers unchanged. If a fact is missing, ask before adding it. Here are my notes: …
Add material deliberately
Use the composer’s plus menu to add an available attachment or choose material from knowledge. Check its name and processing status before sending. A pasted link is an address, not proof that the page was read.
Understand material choices →Continue without losing the point
Stay in the same conversation when the result belongs to the same task. Point to the passage or file you want changed and explain the difference you want to see. Use a new conversation when the subject and required material have changed substantially.
Keep the second and third paragraphs. Rewrite only the opening so that it starts with the problem in my notes. Do not add a personal experience.
For a long conversation, restate important constraints and reselect the material needed for the next request. A visible history does not mean every past message or file will fit into every model request.
Stop or retry a request
Use Stop for the running response and wait until it reports a terminal state. If it still says stopping or reconnecting, do not assume the task has ended. Keep useful text before leaving.
For a failure, read the message first. Fix the connection, access, or input issue, then retry once. A new model call may consume additional quota; retrying is not a guaranteed continuation from the exact point of failure.
Check common failure states →Return to an earlier conversation
Use Recent conversations or search to return to a task. The conversation’s more menu provides actions such as renaming, pinning, and archiving. A short title about the task makes it easier to find later.
Archived conversations can be found through the archived filter in search. Archiving does not stop a running task. Deleting is a separate operation: read the confirmation before proceeding.
Keep a useful response
Use the explicit save-to-library action on a useful response, then open the Copy library to check the saved title and body. Saving a response is separate from keeping conversation history or publishing externally.
Save and organize copy →