Changelog

Import and discovery polish

This release focused on making imported ChatGPT history easier to revisit. We tightened up filters, reduced friction in key navigation flows, and kept smoothing the path from raw export to usable archive.

New & Improved:

• Filters: AI Filters will now enhance your existing compatible filters rather than replacing them.
• Comments: When you open a notification about a comment, the reply input field will now automatically appear.
• Editor:It's now possible to browse through multiple images in the editor without needing to zoom out.
• Templates: When using an existing document to create a template, users can now choose which team to create it in, rather than it defaulting to the first available team.

Fixes:

• Dashboard: Improved consistency when moving between navigation states and filtered views.
• Dashboard: Cleaned up a few edge cases around sidebar ordering and surfaced metadata.
• Desktop Application: Fixed a glitch that allowed PDF printing even in the absence of connected printers.
• Help Center: Enhanced the capability for accessing documentation links directly from the in-app help center.
• Editor:The user mention feature in the SQL editor now respects the 'Display full names' setting.
• Filters:Resolved an inconsistency where filter queries with 'includes any' settings sometimes delivered incorrect results.

For more information, refer to our documentation.

Knowledge graph and search foundations

We invested in the foundations that make My Chat Keeper useful after import: faster search paths, richer organization, and better support for navigating related conversations.

What we improved:

• Enhanced Throughput: Continued improving the responsiveness of content-heavy vaults.
• Dedicated Discovery Workflows: Expanded the building blocks behind search, exploration, and retrieval.
• Controlled Data Access: Kept sharpening the line between account ownership, vault access, and future collaboration patterns.
• Resource Customization: Improved support for larger exports and more varied usage patterns.
• Customization Features: Continued aligning the product around real knowledge-retrieval workflows instead of generic template features.

For more information, refer to our docs post on read replicas or the read replicas section in the documentation.