Managing Chat History: Pin, Fork, Archive, Delete

Your chat history (conversations, past chats, the History list in the sidebar) is saved automatically. This page explains what is saved and who can see it, how you reopen and continue a conversation, where the storage limits are, and how you pin, fork, delete and archive conversations to Confluence. Exporting a conversation as a file is described in Chatting with the AI.

What is saved and who sees it

• Every conversation is saved automatically — you do not have to do anything. Only a Temporary chat (not saved) from the ＋ menu is left out (see Prompts, Skills, Memory and Model Parameters (＋ Menu)).
• After the first answer, a short extra call to the AI produces the title (at most 6 words / 60 characters); it may appear in the list a moment later. If that call fails, the first question becomes the title. The default title of a conversation without a question is "Unterhaltung" — a German word, even in the English interface.
• Conversations are visible to you only — not to colleagues and not to the administration.
• Your history belongs to you as a person and is the same in Jira and Confluence, on the app page, in the fullscreen overlay and on the full page: a conversation started in Confluence is also listed in Jira.
• The list lives in the sidebar under History (with New for a fresh chat). On the app page the sidebar is always there; in dialogs and panels open it with ☰ (Show history). Pinned conversations come first, the rest is sorted by date, newest first. Each entry shows its title and the date of the last message; hovering over an entry reveals the icons for pinning, forking, archiving and deleting. Before your first chat the list reads "No conversations yet."

Opening and continuing a conversation

Purpose — pick up an earlier conversation where you left off. Permission — all users, own conversations only. Before you start — the sidebar with History is open.

Steps

1. Click the entry under History.
2. Type your next message as usual and send it.

Expected result — the messages are loaded. The agent used at the time is restored if it still exists — otherwise the selection falls back to No agent; the model used at the time is restored if it is still available to you, otherwise your current model stays. New messages are appended to the same conversation; the title does not change.

Storage limits

• The most recent 50 conversations per person are kept. On overflow, the oldest unpinned entries are removed first; pinned conversations survive unless all of them are pinned (the limit of 50 remains).
• Each conversation may occupy about 100 KiB. Beyond that it is trimmed at the front: the oldest messages are dropped, the last two messages are always kept.
• Titles are at most 60 characters long.

Pinning and unpinning a conversation

Purpose — keep a conversation at the top and protect it from automatic removal. Permission — all users. Before you start — none.

Steps

1. Hover over the entry and click the star icon (tooltip Pin (stays on top)).
2. To unpin, click the filled star again (tooltip Pinned — click to unpin).

Expected result — the entry moves to the top of the list and is skipped when the oldest conversations are removed. After unpinning it returns to its place in the date order.

Forking a conversation

Purpose — try out an idea or a different direction without losing the conversation so far. Permission — all users. Before you start — none.

Steps

1. Hover over the entry and click the copy icon (tooltip Fork — continue in a copy).

Expected result — a copy is created and opened. It appears in the history with the prefix ⑂ in front of the original title (cut to 60 characters, e.g. "⑂ Sprint planning"); the original stays unchanged. The copy counts as a conversation of its own against the limit of 50.

Deleting a conversation

Purpose — remove a conversation permanently. Permission — all users, own conversations only. Before you start — if you might need the conversation later, archive it first or tick the option in the dialog.

Steps

1. Hover over the entry and click the bin icon (tooltip Delete).
2. The dialog "Delete conversation?" appears with the text "<title>" will be permanently deleted — this cannot be undone.
3. Optional: tick Save to my Confluence archive first — this requires a personal Confluence space (see Archiving a conversation to Confluence).
4. Click Delete permanently — or Cancel (also Esc or a click outside the dialog).

Expected result — the entry disappears. If it was the conversation currently open, an empty chat begins. With the checkbox set, the message "Archived to Confluence." with Open page appears in the sidebar before the conversation is deleted.

⚠️ Warning: Deleting cannot be undone — not by you and not by the administration. If you chose Save to my Confluence archive first and archiving fails, nothing is deleted: the error is shown in the sidebar and the conversation stays.

Archiving a conversation to Confluence

Purpose — keep a conversation permanently as a Confluence page, so that it stays findable and the 50-conversation limit does not affect it. Permission — all users who have a personal Confluence space. Archiving also works while the AnyLLM subscription is inactive. Before you start — you have a personal space in Confluence. If you do not, open your Confluence profile once and create it ("Create personal space").

Steps

1. Hover over the entry and click the archive icon (tooltip Archive to Confluence).
2. Read the dialog "Archive chat to Confluence?": "<title>" will be saved as a page under "AnyLLM Chats" in your personal Confluence space. The chat stays in your history here. Note: the page is as visible as your personal space — you can restrict the "AnyLLM Chats" page to yourself once (child pages inherit view restrictions).
3. Click Archive (or Cancel). While it runs the button reads Archiving … and the dialog cannot be closed.

Expected result — the message "Archived to Confluence." with the link Open page appears in the sidebar (close it with ✕). The conversation now exists as a child page of "AnyLLM Chats" in your personal space. The chat additionally stays in the app history — archiving is copying, not moving.

What the archive looks like

• The parent page AnyLLM Chats is created in your personal space the first time you archive. It contains a short note about visibility, a search field for your archived chats (Search archived chats …) and an automatic list of all archived conversations, newest first.
• The child page is titled "<conversation title> — YYYY-MM-DD HH:MM"; the timestamp is in UTC, not your local time. If you archive the same conversation again within the same minute, seconds are added to the title.
• The page starts with a line "Archived: <date time> UTC · <model>", followed by one block per message under "🙋 You" and "🤖 Assistant (<model>)". The text is written as plain text: Markdown such as **bold** or table syntax appears literally, and suggestion cards are left out.
• Parent and child pages get the label anyllm-chat, so that they stay findable even after being moved. If the label cannot be set, the page is still created without it.
• The page's labels and headings ("You", "Assistant", "Archived") follow the Interface language set by the administration: German only if it is set to German (Deutsch), otherwise English — even if your own interface shows German because it follows your Atlassian language.
• Visibility: the page is as visible as your personal space. If you want the archive for yourself only, restrict the page AnyLLM Chats once via Confluence's Restrictions — child pages inherit view restrictions. This note also appears in the dialog and on the parent page itself.
• Archiving the same conversation several times creates several pages, each with its own timestamp.

Exporting a conversation

To keep a conversation as a Markdown file on your computer instead, use ↓ Export in the header of a dialog or panel, or ＋ → ↓ Export conversation (Markdown) on the app page, in the fullscreen overlay and on the full page. Details are in Chatting with the AI.

Common problems

Related topics

• Chatting with the AI — asking questions, regenerate, export
• Prompts, Skills, Memory and Model Parameters (＋ Menu) — temporary chat and memory
• Getting Started — where the sidebar and the history live
• Permissions, Roles and Data Visibility — who sees what
• Licence, Data Retention and Automatic Deletion — what happens to history data on the administration side
• Troubleshooting · FAQ