Agent Sessions
Resume a conversation without mistaking it for a canvas version restore.
How conversations are stored
The panel saves nonempty message histories through a session API associated with the current workflow ID, or a default scope in local mode. Session saving is distinct from canvas snapshot saving.
- Send a message before expecting the session to appear in history.
- For important canvas changes, also verify the project save state.
Open the history drawer
Use the 《 control in the Agent header to view saved sessions. Selecting a session loads its recorded messages for the same workflow scope.
- Open the Agent, click 《 and wait for the list to load.
- Select a session and read the last request before continuing.
Start a clean conversation
New session resets visible chat, preview and recent event display. It does not clear existing canvas nodes or create a new server workflow.
- Choose New session from the history drawer.
- Describe the next task and reselect any specific canvas references you need.
Know what history does not restore
Loading an old session resets the current preview and runtime events. It does not replay its old pending approval or roll the graph back to the state at that conversation.
- Check the present canvas before requesting edits based on old dialogue.
- Use the project draft recovery path for unsaved graph state, not Agent history.
Handle a missing session
The drawer can delete a saved session. A load or save failure is logged; the history list is not a backup system for your source assets.
- Verify the workflow scope and signed-in account when an expected chat is absent.
- Avoid deleting a session until you have copied any instruction you still need.
Example: continue a shot discussion
Yesterday’s chat may mention a camera move that is still useful today, while the actual image nodes may have changed in the meantime. Treat the conversation as instructions to re-evaluate.
- Load the earlier session and read the chosen shot direction.
- Select the current source image, then ask the Agent to adapt that direction to this node.
If recent messages disappear
Session writes are asynchronous. Navigating away during a failed request may leave a chat missing from the server history even though canvas changes were saved separately.
- Check whether the session is listed in the drawer before relying on it.
- Copy critical instructions outside the chat if connectivity is unstable.