Problem feedback

Please report only one exception per article, and provide basic information such as software version number, device used, model service provider, etc. And keep it as simple as possible. Keep an eye out for similar feedback, and comment or vote if you already have one.
Key feedback on the “Compress Conversations” feature - Request to restore the v1.18 logic
Subject: Key feedback on the “Compress Conversations” feature - Request to restore the v1.18 logic I'm writing to provide feedback on major and unfortunate changes to the core “compress conversations” functionality between the 1.16.1 and 1.19.0 versions. In v1.16.1 (2025-09-17), you introduced the “Compress conversations” feature. Its original and powerful implementation allows users to generate an intelligent summary of the current conversation and then launch a brand new chat session as a system prompt/instruction. This enables the logic, intention, and context of the previous conversation to be seamlessly carried over to the new stage, effectively enabling long-term project-like collaboration and overcoming the limitations of the context window. However, in v1.19.0 (2026-02-11), this functionality was quietly and radically modified. The digest is now inserted as a regular user message in the same chat thread. This change completely reduces the usefulness of this feature: Loss of core functionality: It no longer creates new, easy-to-manage chat sessions. The compressed summary and follow-up conversations are buried in existing, increasingly lengthy, and difficult to manage chat history, making organization impossible. Broken workflow: The original purpose of the feature — to provide a concise, authoritative “briefing” for a new stage of discussion — has disappeared. AI no longer sees summaries as high-priority instructions (system prompts), but simply another context. Bad user experience (automatically triggered): The new “auto compression” is disruptive at ~ 60% context length. It cruelly interrupts deep and fluid conversations to save meager tokens, prioritizing system management while ignoring user intent and creative flow. For users working on complex, lengthy reasoning and projects (a key advantage of advanced artificial intelligence), the v1.18 era's “compressed conversation” isn't a “token saver” — it's a must-have workflow engine. Strongly requested: I would highly recommend that development and product teams revert the “compress conversation” functionality to the pre-v1.19 logic, as shown in v1.18.x. Please restore its ability to generate a summary and use it as a system prompt to launch a new standalone chat session. Ideally, this feature would be made back to default, or at least provided as an explicit user option. The current implementation addresses a problem that doesn't exist (for advanced users) while undermining critical and unique capabilities. Thanks for your consideration.
0
Load More