> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/no-code-experiences/chat-experiences/manage-your-chat-experiences.md).

# Manage your chat experiences

Find, search, rename, duplicate, and delete the chat experiences on your account, and run the same characters against different wording.

Every chat experience you create stays on **My Experiences** until you delete it. Use this page to find one again, to rename it, to delete it, and to duplicate it when you want to run the same kind of conversation with a different brief.

### Find a chat experience

Chat experiences are listed in the **Chat experiences** section of **My Experiences**, above the **3D experiences** section. See [Open My Experiences](/api-docs/no-code-experiences/chat-experiences/open-my-experiences.md) for how to reach it. The heading carries the number of chat experiences on the account.

Selecting a card or a row opens a new room from that experience. It does not reopen the last conversation.

Three controls work on that list:

| Control                                    | What it does                                                                                                                                                                       |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Search chat experiences**                | Filters the list. Every word you type has to appear in the experience name or in its purpose. A search with no results shows **No chat experiences match your search.**            |
| The two view buttons beside the search box | Switch between a grid of cards and a list of rows. The browser remembers your choice. On a narrow window the list falls back to the grid, because the row cannot hold its columns. |
| The three-dots menu on a card or row       | Opens **Previous sessions**, **Rename**, **Duplicate with a new brief**, and **Delete** for that experience.                                                                       |

**Previous sessions** opens the conversations already run from that experience, each one a transcript you can read but not add to. See [Chat Experiences](/api-docs/no-code-experiences/chat-experiences.md).

The grid shows a card per experience: its room type, its name, the first two lines of its purpose, and a session line reading either **No sessions yet** or the number of sessions and when the last one ran. The list shows the same experiences as rows, adding an **ID** column carrying the room ID, which you can copy from the row.

If the section reads **No chat experiences yet**, nothing has been created on the account. See [Create a chat experience](/api-docs/no-code-experiences/chat-experiences/create-a-chat-experience.md).

### Rename a chat experience

Renaming changes the label on the card and in the room's top bar. It does not touch the brief.

{% stepper %}
{% step %}

#### Open the rename dialog

Open the three-dots menu on the experience's card or row and select **Rename**.

The **Rename chat experience** dialog opens with the current name in the **Name** field.

An open room has its own route to the same rename. The pencil beside the room name and **Rename experience** on the top bar's three-dots menu both open a **Rename experience** dialog with an **Experience name** field.
{% endstep %}

{% step %}

#### Save the new name

Type the new name and select **Save**.

The field grays out and shows **Saving…** while the change is being stored, and the dialog closes once it has been.
{% endstep %}
{% endstepper %}

### Duplicate an experience with a new brief

**Duplicate with a new brief** is how you run the same kind of conversation against different wording. The room type, the purpose, and the briefing are fixed when an experience is created, so changing any of them means creating another experience—and duplicating starts you from the original rather than from a blank dialog. See [Why the brief cannot be changed](/api-docs/no-code-experiences/chat-experiences/the-room-brief/why-the-brief-cannot-be-changed.md).

To put the same characters through a different brief, duplicate the experience, change the wording, and add those characters to the new room.

{% stepper %}
{% step %}

#### Start the duplicate

Select **Duplicate with a new brief**. It appears on the three-dots menu on the experience's card or row, on the three-dots menu in an open room's top bar, and in the tooltip on the room's **Fixed at creation** label.

That label sits in the room's side panel, and on the pinned **Room brief** card while the room is still empty.
{% endstep %}

{% step %}

#### Change the wording

The **Create a chat experience** dialog opens prefilled from the original: the same room type, the same purpose, the same briefing if one was written by hand, and the original name with `(copy)` after it.

Every field is editable, because this is a new experience rather than an edit of the old one. Change the purpose, the room type, the briefing, or all three.

The **Custom** room type has one exception. While its purpose is empty and no briefing came across from the original, the briefing box shows an example of what a briefing looks like instead of taking your typing.
{% endstep %}

{% step %}

#### Create it

Select **Create experience**.

The duplicate opens as its own empty room and appears as a separate card on **My Experiences**. The original is untouched, and its previous sessions stay with it.
{% endstep %}
{% endstepper %}

### Delete a chat experience

Deleting removes the experience from **My Experiences**, along with its list of previous sessions.

{% hint style="danger" %}
Deleting a chat experience cannot be undone. The dialog says so, and there is no way to restore the experience or its previous sessions afterwards.
{% endhint %}

{% stepper %}
{% step %}

#### Open the delete dialog

Open the three-dots menu on the experience's card or row and select **Delete**.

The **Delete chat experience** dialog names the experience and asks you to confirm.
{% endstep %}

{% step %}

#### Confirm the deletion

Select **Delete** to confirm, or **Cancel** to keep the experience.

The card disappears from the list, and a confirmation message reports that the chat experience was deleted.
{% endstep %}
{% endstepper %}

### Next steps

The brief you duplicate here is fixed for a reason, and the section that explains it also covers how a briefing is written. Creating an experience from scratch starts in the same dialog a duplicate opens.

{% content-ref url="/pages/UegeFZ5XJFnX4nKGvMoP" %}
[Why the brief cannot be changed](/api-docs/no-code-experiences/chat-experiences/the-room-brief/why-the-brief-cannot-be-changed.md)
{% endcontent-ref %}

{% content-ref url="/pages/Th74Pt0L3LuXdoZaQU34" %}
[Create a chat experience](/api-docs/no-code-experiences/chat-experiences/create-a-chat-experience.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.convai.com/api-docs/no-code-experiences/chat-experiences/manage-your-chat-experiences.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.