Conversations & History

Your past conversations live in a right-hand sidebar. Click the History button in the top bar to slide it out — you'll see your recent chats, a search box, and per-row actions. The New button — also in the top bar — starts a fresh chat. This page covers what each control does and how it interacts with the agent and instance selectors.

The "New" button

New clears the chat area and starts a fresh conversation using your tab defaults:

the agent currently in the Agent Selector,
the instance currently in the Instance Selector,
your tab's reasoning level.

It does not ask the server for anything until you send your first message — so pressing New is free.

Opening an old conversation

Open the history sidebar from the History button in the top bar and click a conversation to load it into the chat area. While it is open:

The top-bar agent selector shows the conversation's agent. Choosing another item there starts a new chat or opens its workspace; it does not reassign the open conversation.
To intentionally change the agent for the open conversation, use + → Agent in the message box.
The instance selector is read-only and shows the connection bound to the conversation.
Pressing New snaps both selectors back to your tab defaults.

Each row in the history sidebar has a ⋯ menu (also available via right-click):

Properties — opens a dialog with the conversation's full metadata: title, ID, status, type, created / updated timestamps, agent (key + name), instance connection ID, reasoning level, app / site IDs.
Rename — change the title.
Delete — soft-deletes the conversation. It disappears from the list but can be restored by support if needed.

Queue your next message

You don't have to wait for an answer to finish. While the agent is working, type your next message and press Enter (or the clock button next to Stop) — it is added to the queue instead of interrupting.

Queued messages appear as small cards just above the message box, in the order they will run.
Each card has Edit (change the wording before it runs) and Remove.
When the current answer finishes, the first queued message is sent automatically and the answer streams as usual.
The queue is kept for you, not just for this browser tab: reload the page, or come back on another device, and your queued messages are still there and still run.
If another browser tab tries to start an answer for the same conversation at the same moment, that extra attempt is refused instead of running alongside the first answer.

Example: you ask "Analyse last month's sales by region", then immediately queue "Now compare it with the same month last year" and "Summarise both in three bullets". All three run one after the other, in order.

Putting the queue on hold

Pressing Stop stops the current answer and holds the queue, so nothing queued starts on its own. The cards stay in place and a small bar appears: Queue on hold — Resume.

Press Resume to continue from the first queued message.
Sending a new message yourself also clears the hold.
While on hold you can still edit or remove anything in the queue.

The Apps filter

The Apps filter in the history sidebar shows two kinds of conversations:

App Builder chats that haven't created an app yet. Once the app exists, its builder chat is opened from the app itself, not from History.
AI runs started by your apps from the last 7 days. For example, when an app button like "Analyse with AI" sends a file to the AI, that run shows up here right away. A green dot on the History button means it is still running. Open it to see what the app sent, which tools ran and what the AI answered, or why it failed.

AI runs started by apps are visible to Power users and above, either on the platform or in the instance you have selected. They are removed automatically after 7 days.

Search

The search box at the top of the history sidebar filters by title and message content. Results highlight the matching snippet.