A session keeps a project's conversation available across visits. Return to it to continue a task with its history, or start another session for different work.
#Create
- Select the project.
- Choose New session under the intended folder.
- Choose an installed provider.
- Select Create.
- Check model and permission mode before sending a request.
Cancel the inline creation row to abandon it before completion. If the connection drops during creation, inspect the session list before pressing Create again. A real session can exist even when your browser misses its acknowledgement.
Folders organize sessions; they do not create a new repository or branch. Sessions using the same directory can edit the same files.
#Resume
Select an existing session from its folder or a search result. Wait for replay to finish before continuing. Scroll upward to load earlier messages when necessary.
A resumed conversation may restart its provider process or need authentication. Readable history does not establish readiness to execute. After an interruption, request a concrete next step: “Inspect current Git status and determine whether the previous validation finished before continuing.”
The latest visible response, pending queue, and actual files together provide the useful recovery context. Do not infer success from the absence of a spinner.
#Rename and organize
Open the session menu and choose Rename, or use the title's rename affordance. Enter saves; Escape cancels; leaving the field saves a changed nonempty title. A connection or permission change can cancel the edit.
Choose a descriptive task title, such as “Fix export validation,” rather than a provider name. Move the session into a folder for related work. A saved View displays several sessions without merging their transcripts.
#Finish deliberately
Use Stop for execution. The pane's Close action changes presentation and is not a substitute for stopping. Check pending messages before resuming.
To remove a session, right-click its sidebar row and choose Delete, then read the confirmation. Preserve lasting project outcomes in Project Logs and reference material in repository documents before deleting history. For an alternative investigation path, see Fork and rewind. For access, see Session privacy.