History and library
The library holds every generation you have made in one searchable list, filtered by kind, platform and date, with the filter state carried in the URL so a filtered view can be linked or bookmarked. Search matches the generated output rather than the source material, and export always reflects the filter you are looking at rather than quietly returning everything.
What it holds
Every generation you have made — comment replies, DM and email replies, summaries, explanations, rewrites, planner posts and image prompts — in one list rather than four separate tabs.
Older links to the previous history screens still work; they redirect here and carry their filter across.
Searching and filtering
Search matches the output — the text that was generated — not the post or thread it came from. That is usually what you want, because you remember what you wrote rather than what you were replying to.
Search characters are treated literally, so a term containing % or _ searches for those
characters rather than acting as a wildcard.
Filters refine, they do not cross. The kind filter narrows within a category rather than reaching across into a different one, so a filter combination can never return something that contradicts itself.
Only filters that could return something are offered. A platform with no rows does not get a checkbox — a filter guaranteed to return nothing is worse than no filter.
The state lives in the URL. A filtered view can be bookmarked, shared with a teammate, or reloaded without losing your place.
The rail counts describe the whole library, not the filtered slice — the same principle as the planner's stat tiles. A count that shrinks as you search reads like progress rather than like a filter.
Export
Exports what you are looking at. The export path and the page share their filter logic, so "export selection" cannot quietly hand you everything when you asked for a narrowed set.
Costs
Where a generation has a recorded cost, the library shows it. A run made on your own AI provider key has no cost recorded against your credits — the field is blank rather than zero, because zero would assert it was free when in fact it was billed by your provider.
Money and model detail are visible only to accounts with the appropriate permission. On other accounts those columns are absent rather than hidden — the restriction is enforced where the data is served, not painted over in the interface.
Retention
Generations are kept so you can search and reuse them. Where a retention period is set on the workspace, older entries are removed by a scheduled job once they pass it.
Shortening a retention period deletes history that is currently visible, so that change asks for confirmation before it applies.
Limits
- The library records what was generated, not what you finally sent — if you edited a draft before sending, the edit is not captured.
- It is per account. It is not a shared team archive.
- Deleting an entry removes it from your history; it does not recall anything you already posted.
If you are trying to remember a good reply you wrote last month, search for a phrase from the reply itself rather than from the post you were answering.