To the chatbox development and product team: Subject: Important feedback on the “Compress Conversations” feature - Request to restore the v1.18 version of the logic I'm writing to give feedback on a major and unfortunate change to the core “shrink conversations” feature between v1.16.1 and v1.19.0. In v1.16.1 (2025-09-17) , you introduced the “Compress conversations” feature. Its initial powerful and effective implementation was to allow users to generate an intelligent summary of the current conversation and then use that digest as a system tip/instruction to launch a brand new chat session . This allows the logic, intent, and context of previous conversations to be seamlessly carried over to a new stage, effectively enabling long-term, project-like collaboration with AI by overcoming the limitations of the context window. However, in v1.19.0 (2026-02-11) , this functionality was silently and completely changed. The digest is now inserted as an ordinary user message into the same chat thread. This change completely reduces the usefulness of this feature: Loss of core functionality: It no longer creates a new, manageable chat session. The compressed summary and subsequent conversations are buried in the growing, increasingly lengthy and cluttered history of existing chats, making organization impossible. Workflow broken: The original purpose of the feature — to provide a clear, authoritative “brief” for the new discussion phase — has disappeared. AI no longer sees summaries as high-priority instructions (system prompts), but just another piece of context. Poor user experience (automatically triggered) : The new “automatic compression at around 60% of the context length” mechanism is disruptive. It grossly interrupts deep, smooth conversations, simply to save the minuscule number of tokens, which prioritizes system management and ignores the user's intention and creative thought flow. For users working on complex, lengthy reasoning and projects (a key advantage of advanced AI), the v1.18 era's “compressed conversation” isn't a “token saver” — it's an essential workflow engine. Strongly requested: I strongly urge the development and product teams to revert the “compression conversation” feature to the pre-v1.19 logic, that is, to the state seen in version v1.18.x. Please restore its ability to generate a summary and use this as a system prompt to launch a new, standalone chat session. Ideally, make this the default behavior again, or at least provide it as a clear and unequivocal user option. The current implementation solves a (minor) problem that doesn't exist for advanced users, but it destroys a critical and unique ability. Thank you for your attention.