Conversation history
Nothing has to be saved by hand. Every question answered on the Answers page and every agent chat becomes a conversation, kept under the account that started it and reachable again from a list. This page covers where those lists are, what each row action does, how a conversation is opened to a colleague, and what a conversation still holds after it is deleted.
Two lists, one per product
Answers and agent chat keep separate lists, because a transcript of an agent run and a written answer are not the same thing to come back to.
| Product | Where the list is | How a conversation opens |
|---|---|---|
| Answers | The Conversations button in the Answers header | Its own page, at a link that can be bookmarked |
| Agent chat | The Conversations button in the Agent header | The chat, reloaded in place |
On both pages the button opens a panel that lists that product's conversations, and it is the only place an answer conversation is found, renamed, starred or removed. On the Agent page New chat beside it starts a fresh one.
A conversation belongs to the person who started it. A colleague in the same workspace cannot list it or open it, and being an admin grants no override. The owner can open one conversation to named colleagues, which is covered under Sharing a conversation below. The changes ledger is the opposite case and is shared across the whole workspace. See Changes and approvals.
Both lists put starred conversations first, then the most recently active ones.
Finding one again
Each list has its own search box, and both are free. The term is matched against the conversation's name and against every question and answer inside it, which is what makes them worth searching: a conversation is named automatically from its first message, so a list of names often says what was asked and never what came back. Searching for a term that appears only in an answer still finds the conversation that discussed it.
A term is capped at 200 characters. Clearing the box restores the full list. A term that matches nothing says so, in different words from an empty list, so a search miss is never mistaken for lost work.
Both panels have a search box at the top that narrows the list as you type, and it costs nothing: it is a database query over the conversations already kept. It is separate from asking a question, which is the box on the front door and the one that spends.
Row actions and reopening
The menu at the end of a row carries five items on a conversation the account owns.
- Star pins a conversation above every unstarred one. Starred rows keep their own most-recent-first order. Unstar returns the row to the main order.
- Rename replaces the automatic name with up to 200 characters. Enter saves it. Escape or a click elsewhere cancels, and an empty name is refused rather than stored. A rename does not move the row: the order follows real activity in the conversation, and renaming is not activity.
- Share with opens the conversation to colleagues of the same workspace. See Sharing a conversation.
- Delete removes the row from the list, as described below.
- Open in new tab opens the conversation in a second tab. It is an ordinary link, so a middle click or a modifier click on the row itself does the same thing.
A row a colleague shared carries only Open in new tab. Starring, renaming, sharing and deleting belong to the account that started the conversation.
Reopening shows what can be honestly replayed, which differs between the two products.
On the Answers page, a reopened conversation shows its most recent question, that answer, and that answer's own sources panel. Earlier turns are not re-rendered. A link to a conversation that has been removed says so instead of failing.
On the Agent page, a reopened conversation restores the question and answer turns and continues in the same conversation, so a follow-up still has context. The conversation pane shows what the agent remembers. The plan and the terminal show what its runs executed, step by step, and the run header shows how the latest run ended. Very old steps are listed with their command and output marked as no longer kept. A conversation whose latest run is still going, or is waiting for an approval, opens on that run as it happens, with the approval card in place.
An agent conversation outlives the environment it ran against. Deleting an environment keeps its conversations as read-only history, so one whose environment is gone still opens to be read but shows a notice in place of the question box, and continuing that work means starting a new chat for another environment.
Sharing a conversation
A conversation is private by default. The owner opens one to named colleagues of the same workspace, one permission each, and nothing else about it changes.
Share with is in the row menu on both lists, and in the Agent header while a conversation is open. It lists the workspace members, excluding people who have been invited but have not signed in yet. Ticking a colleague grants access. Choosing Done saves the whole list at once, so a colleague unticked in the same visit loses access in the same press.
The list shows three colleagues at a time. A search box above it matches on email address and on name, and arrows below it move through the rest. A workspace of fifty is meant to be searched rather than scrolled. Ticks are kept while paging and while searching, so granting access to fifteen people out of fifty is one visit and one press of Done. The count next to that button says how many are ticked.
| Permission | What it allows |
|---|---|
| Can view | Read the conversation and follow it as it goes. |
| Can participate | Read it, ask in it, and start agent runs in it. |
Three rules follow from the owner keeping the conversation.
- Only the owner shares, renames, stars or deletes it. A colleague with Can participate cannot pass it on to anyone else.
- A colleague never sees who else the conversation is open to. The list of people is shown to the owner alone.
- Removing a colleague takes it out of their list at once, and a bookmarked link to it stops working for them. Deleting the conversation removes it for everyone.
A shared conversation refreshes itself every few seconds while it is on screen, so a turn added by a colleague appears without a reload. Each turn is labelled with who asked it when the reader is not the author. A colleague with Can view sees why they cannot write where the question box would be.
Questions and agent runs started by a colleague spend the workspace credit exactly as the owner's do, and count against the same monthly budget. See Billing.
Sharing sends no notification today. A shared conversation appears in the colleague's own list, marked with the email of the person who shared it.
Removing a conversation
Delete asks for confirmation, and the confirmation is worded carefully. It offers to remove the conversation from the history, and that is exactly what happens. A removed conversation is hidden, not erased. Its questions and answers are retained, so the removal is recoverable and the transcript stays available for support. Removing the same conversation twice is harmless.
The docs claim nothing beyond that. The only operation that erases stored conversations is deleting the workspace, which purges every record belonging to it.
Rating an answer
Under a written answer, a Useful? control offers Yes and No. Choosing one records the rating against the conversation and replaces the control with an acknowledgement.
One rating is kept per conversation, the most recent one, so rating a later answer in the same conversation replaces the earlier rating. A rating changes nothing on screen beyond the acknowledgement and never triggers a new answer. Agent chat has no equivalent control.
A rating is recorded against the conversation rather than against the reader, so it is offered to the owner and to a colleague with Can participate. A colleague with Can view sees a note in its place.