Sessions
A session is a persistent conversation thread with its own working context. The Conversations tab is the full manager.
In the agent bar, a counter shows your unread sessions and those shared with you. Hover over the counter to see their titles; looking at it does not mark them as read. Sessions that are still in progress are left out. The counter goes down after three seconds of continuous reading in the chat, in the foreground, once the reply is finished. This state is personal. In the list, an unread session is recognisable by its dot and its bold title; once read, it stays where it is.
What you can do
Section titled “What you can do”- create a new session;
- open or resume an existing session;
- add a session to your favourites to keep it at the top of the list;
- search by title, preview or identifier;
- filter by channel, for example portal, email or Telegram;
- show only your unread sessions with the Unread filter;
- rename a session;
- delete a session;
- clean up your old finished sessions (see below).
Three tabs organise the conversations:
- Me: your sessions and those shared with you;
- Team: the conversations of your colleagues that you can see, those they have shared with you and those that have no Diadems creator, such as those from a messaging channel;
- Automations: the runs of scheduled tasks and webhooks.
In Team, the menu next to the search shows all members, a single colleague, or No owner. Email threads have their place in the inbox of the Email tab.
Each row shows the full title (hover over it if it is long) and the time of the last activity. Below, a discreet line only flags what is out of the ordinary: the person who created the session if it is not you, sharing, the channel when it is not the chat (Email, Webhook, Scheduled task…), read-only status, and the number of messages. Hover over this number to see the actions taken, the model calls and the tokens, with the breakdown of input, output, reasoning and cache, without the provider’s technical costs. The star and the ⋯ menu appear when you hover over the row; the star of a favourite stays visible.
On a phone, the star and the ⋯ menu stay visible at the end of the row, and an extra row shows the sites and files actually encountered in recent exchanges. From a conversation, swipe from the left edge of the screen to go back to the list of sessions.
A continuation after compression is flagged without exposing the internal technical identifiers.
When a session is still working, it automatically moves up into the In progress now group. A badge shows whether it is running, waiting, retrying or waiting for an approval. The status updates without reloading the page and disappears as soon as the work is finished.
Conversations and automations
Section titled “Conversations and automations”The tab distinguishes two histories:
- Conversations: Diadems Chat and messaging apps such as Telegram or Discord;
- Automations: scheduled tasks, webhooks and jobs started by an integration with no conversation opened by a user.
The Automatic processing label refers to an internal command used by Hermes or by a former integration. It is not a terminal that the customer needs to connect to. Long lists are displayed progressively and can still be filtered by origin.
A finished run of a scheduled task can be continued with Continue the conversation: the first administrator who does so becomes its pilot and the run joins their sessions, with its Scheduled task badge. See Scheduled tasks. Telegram conversations remain view-only in Diadems. An email thread is resumed with Continue in the chat, from the inbox of the Email tab: see Email.
With a shared plan, administrators see the sessions grouped by their creator. A session belonging to another member opens read-only: the administrator can view its history, but cannot send a message, rename it, compact it, delete it or interrupt its work. Its in-progress status stays visible so that you know right away that another member or an automation is using the agent. A user only finds their own sessions. The agent receives the authenticated identity of the person talking to it, even when several colleagues use the same agent. This identity uses the first name used by agents set in the Team section, and not necessarily the name of the Diadems account holder.
Favourites are specific to your account. Diadems only keeps the opaque identifier needed for this ranking; the title, messages and history stay in the agent’s capsule.
The Share the conversation button in the conversation header opens a small window, without leaving the thread. With members gives read and write access to the people ticked; By link opens the session in Read or Write to members who have access to the agent, or stays Off. Each change applies straight away. As with a shared document, anyone who can write in the session can also share it in turn. Standard or restricted visibility is set at creation; an administrator can Take control of a standard session that is idle, and the pilot can Hand back control to its creator. See Profile and team. On a small screen, the Other conversation actions menu groups sharing and search. Click the title directly to rename a session you are allowed to edit.
New session
Section titled “New session”New session starts again with a blank working memory.
To start again from a specific point in a conversation, open the ⋯ menu of a message and choose New conversation from here. The new conversation takes the history as it was at that moment, the agent’s work included, and the original conversation stays untouched:
- on one of your messages, the copy stops just before it and its text waits for you in the composer, so you can edit it and send it;
- on an agent reply, the copy stops after that reply;
- on the very last reply, it takes the whole conversation (not while the agent is working).
The new conversation belongs to you, with the same profile and the same model; its sharing is not copied. A message summarised by a compression of the conversation can no longer be used as a starting point. The action only appears on agents whose version supports it.
A new session stays a local draft until you have sent a message. It therefore appears neither in the list nor in the counters. On the first send, Diadems assigns it to your account and Hermes creates it in the capsule; if you leave the draft without writing, no empty session is kept.
Delete a session
Section titled “Delete a session”Deleting requires write access to the session. Deleting removes this session’s history. It does not automatically erase the agent’s long-term memory or its other sessions.
Clean up old sessions
Section titled “Clean up old sessions”Check and clean up, at the bottom of the tab, looks for the chat sessions you control that are finished and have been inactive for more than 90 days. Their number is shown before anything is deleted: nothing is deleted without your confirmation.
The check and then the purge move forward in small steps, with their progress shown, so as not to block a very busy agent. You can cancel the check, or stop the purge between two batches. Each session is checked again just before it is deleted: a session resumed in the meantime is kept.
If the agent is too busy, the check may stay partial; the message says so and you just need to run it again later. The result only counts the deletions confirmed by the agent.