Problem
A conversation from Tuesday contained the one good explanation of a thing, and it’s now the fortieth item in a list of auto-generated titles. The viewer remembers a single distinctive word from it and has no way to search on that word.
Solution
The list is a filing system nobody agreed to maintain, so almost everything about it has to work without effort from the viewer.
The title is the first problem. It’s generated from the opening message, which means a conversation that began with “quick question” is filed forever under “quick question”. Generating the title after a few turns rather than from the first message produces a far better list, since by turn three the actual subject exists. Letting the viewer rename is necessary and used by almost nobody, so it can’t be the primary mechanism.
Search is the part that actually rescues the pattern, and it has to run over message bodies rather than titles. Title search fails precisely in the case the viewer is in: they remember a word from the middle of an exchange, which is exactly the word no title contains. Full-text search across conversations turns a dead archive into a resource, and its absence is the single most common complaint about this pattern.
Grouping by recency is close to universal and close to right, because relevance decays fast. The tail is the hard part. A list that grows forever with no pruning, no archive and no sense of which items mattered becomes a place things are lost rather than kept. Pinning is the cheapest fix. Grouping into projects or folders is the heavier one, and it repays itself for people who work in a few recurring contexts.
Two controls belong here that are easy to treat as settings rather than as part of the list. The first is deletion, and it has to say what it actually does: removing a conversation from the sidebar, removing it from the provider’s storage, and removing it from a training corpus are three different operations and people assume the strongest one. The second is the ability to have a conversation that never enters the list at all. Google’s temporary chats are the clearest shipped form of this, and the documented behaviour is specific: they stay out of recent chats and Gemini Apps Activity, aren’t used for personalisation or model training, and are retained for up to 72 hours to handle the response and any feedback. Retention stated to the hour is the precision this control needs. A vague promise about an ephemeral conversation is worse than no promise at all.
Use when
Conversations have value beyond the session, which is nearly always true once an assistant is used for work.
Don’t use when
The assistant is scoped to an object that already has its own history, like a document or a ticket. There the conversation belongs with the object, and a parallel global list splits the record in two.
Trade-offs
Persistent history makes the assistant useful across days and creates a retention surface that has to be explained, controlled, and defended. Auto-generated titles are the only titles that will ever exist at volume, and they’re mediocre by construction. Projects and folders add real organisation and add a filing decision at the moment someone wants to ask a question. A sidebar of recent conversations is a privacy exposure in any shared or screen-shared context—a design problem rather than a settings one.
Checklist
- When is the title generated, and from how much of the conversation?
- Does search cover message bodies or only titles?
- What does the list look like at a thousand conversations?
- Is there any way to mark something as worth keeping?
- Does delete remove it from the sidebar, from storage, or from training data, and does the wording distinguish those?
- Can a conversation be started that never enters the list?
- If so, exactly how long is it retained and for what?
- Is the list visible during screen sharing, and can it be hidden quickly?
- Can a conversation be exported or shared without the rest of the history?
- Does the list say anything about which conversations the assistant draws on later?
Compare
ChatGPT groups by recency with generated titles, and supports renaming, archiving and project grouping. The sidebar gets treated as a working filing system. Gemini pairs the list with temporary chats and a published retention window, which makes the decision to persist an explicit one taken per conversation. Claude leans on projects, so the primary unit is a body of work with its own knowledge rather than a flat reverse-chronological list. Slack has no separate list at all, because an AI exchange lands in a channel or DM and inherits the search, retention and permission model the workspace already has.
Related
Memory chip is the other persistence layer and the one people confuse with this. First-run state has to offer a path into this list. Message turn is the unit these entries are made of. Custom instructions persist across every item here. Scoped context is what a project adds on top of a plain list.