> For the complete documentation index, see [llms.txt](https://docs.aisuru.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisuru.com/en/sharing/conversations/conversation-history-and-resume.md).

# Conversation history and resume

Chat history lets users access, review, manage, and resume their previous conversations with an AIsuru Agent.

Instead of treating every interaction as an isolated exchange, users can return to earlier conversations and continue from where they left off.

### Open your chat history

Chat history is available from AIsuru widgets without requiring additional configuration from the Agent creator.

To open it:

1. find the chat-history icon in the widget toolbar;
2. select it to open the history page;
3. browse your previous conversations with the Agent.

> **Note:** Chat history is also available when using the Agent in **Try** mode.

### Browse and filter conversations

The history page provides controls for finding and reviewing previous chats.

#### Download the current chat

You can download the conversation currently being viewed as a `.txt` file.

#### Filter by date

The documented time filters include:

* All;
* Today;
* Yesterday;
* Last 7 days;
* Last 30 days.

#### Filter by minimum number of messages

You can also filter conversations according to the minimum number of messages.

The documented options include:

* Any;
* 2;
* 3;
* 5;
* 10;
* 15;
* 20;
* a custom value.

### How conversations are shown

Each conversation in the history includes information that helps you identify it quickly.

#### Automatic title

The conversation title is generated automatically from the user's first message.

If the message is too long, the title is truncated with `...` to keep the list readable.

#### Date, time, messages, and media

The history also shows information such as:

* the date and time when the conversation started;
* the number of messages and media exchanged.

Conversations are ordered from the most recent to the oldest.

### Open a previous conversation

Select a conversation from the list to open its full history.

The detailed view preserves:

* all messages exchanged in the conversation;
* the conversation context and session data;
* the familiar presentation of the original widget.

### Resume a conversation

From the detailed conversation view, use **Resume** to continue the chat.

When a conversation is resumed:

* the user returns to the previous discussion;
* the Agent continues with the context of that conversation;
* the original conversation environment is restored;
* the chat resumes using the corresponding widget/layout configuration.

This is useful when a conversation develops over time or when the user needs to return to information discussed previously.

### Conversation history and privacy

The documented chat-history behavior includes the following protections:

* each user sees only their own conversations;
* conversations remain available after the browser is closed;
* conversations are associated with the user account;
* history management does not require manual intervention from the Agent creator.

### Session IDs and conversation resume

Each conversation has a unique `sessionID`.

When a user resumes a conversation through chat history, AIsuru restores the session associated with that conversation.

This also makes session information relevant to advanced integrations and API-based experiences.

> **For developers:** User-facing chat history and programmatic session resume should not be treated as the same workflow. The current Frontend documentation states that when a `sessionID` is supplied directly to a component, AIsuru validates it: a valid session repopulates the chat, while an invalid session starts a new conversation. That Frontend documentation also currently states that directly resumed sessions expire after one hour of inactivity. Follow the current Frontend documentation when implementing session persistence programmatically.

For developer-controlled session handling, see Advanced embed and web integration and the Frontend **Session resume** documentation.

### Why chat history is useful

#### For users

Chat history provides:

* **continuity:** conversations can continue over time instead of restarting from zero;
* **historical reference:** users can review information, suggestions, or answers received earlier;
* **flexibility:** users can interrupt a conversation and return later;
* **less repetition:** information already discussed remains available in the previous chat.

#### For Agent creators

Persistent conversations can support:

* stronger returning-user engagement;
* longer and more developed conversations;
* less repetitive interaction;
* better understanding of how users interact with the Agent over time.

### Best practices

To make conversation resume more useful:

1. design conversations so users can naturally continue them later;
2. use temporal references appropriately when the Agent refers back to earlier parts of a discussion;
3. structure conversational flows so they can progress over multiple interactions;
4. test the resume experience regularly.