Conversation history
Find the agent's earlier conversations and resume the one you want — when that provider offers a catalogue and when the conversation is resumable in that context.
The Conversation screen has a conversation history browser: the list of conversations that agent has already had, with search, and the action to resume one of them in the session you choose.
The history belongs to the provider, not to the application. The application queries the catalogue the agent keeps — it does not hold a parallel copy of your conversations in order to display them there.
Who has a catalogue
The catalogue is available for Claude, Codex, OpenCode and Grok. Verboo, Cursor, Hermes and Pi do not expose the catalogue port: on them, the browser does not present native history.
Do not present native history as available for a provider that does not have the port — the absence is declared, not simulated.
Resuming a conversation
Each row in the list offers resume. The action is not guaranteed merely because the conversation exists, and the result is classified:
| Result | What it means |
|---|---|
| Resumed | The session was resumed, with the conversation’s reading position. |
| Missing | The conversation is no longer there. |
| Authentication required | A valid credential is missing for that provider or host. |
| From another context | The conversation belongs to a different context from the current one, and therefore cannot be resumed here. |
| Unsupported | That provider does not know how to resume. |
| Failed | An error along the way, with the reason’s detail. |
The “from another context” case is the most important one to know, because it explains a dimmed button: when the conversation belongs to another scope, the resume button appears disabled with the reason in view — “From another context” — instead of failing after the click. A context filter can block resuming, and the screen says so before you try.
The list has a manual reload and pages in blocks: reading does not load the whole conversation, and does not start an agent session just to list. Listing history does not execute the agent.
Other actions in the same list
Alongside resume, the list offers, where applicable:
- Create a fork — open a new conversation from that one.
- Continue in another agent — move the conversation to another provider, when the transfer panel is present.
- Archive, remove the binding and delete at the provider — operations with effects of their own, because they touch your data.
- Export — as JSON or Markdown, covered in Exporting the history.
Limits worth knowing now
- Resuming depends on context and credential. A listed conversation may not be resumable, and the screen reports the reason instead of hiding the row.