功能建议

It is recommended to modify the bottom text input area to an adjustable input box instead of a fixed one

Cleaning up a conversation list takes a bit of time. 2 ideas: Have the Clear Conversation list have an option to keep all starred items. Put a delete icon above the Up/Down arrows in the response window to minimize clicks.

用谷歌生图现在只能默认1k但是谷歌那边支持的是1k 2k 4k希望后续生图能支持一下

比如添加的时候可以用逗号或者分号进行批量添加，现在只能一个一个手动添加太麻烦了

目前的聊天没有分类功能，只有简单的收藏分类，所以建议增加新的分类（文件夹）功能，可以把不同类别的ai聊天归类

聊天里面增加已经提问的目录来 这样方便进行跳转

致聊天框开发与产品团队： 主题：关于“压缩对话”功能的重要反馈——请求恢复 v1.18 版本的逻辑 我写此信是为了反馈在 v1.16.1 到 v1.19.0 版本之间，对核心“压缩对话”功能进行的一项重大且令人遗憾的改动。 在 v1.16.1 (2025-09-17) 中，你们引入了“压缩对话”功能。其最初强大且有效的实现方式是：允许用户生成当前对话的智能摘要，然后将该摘要作为 系统提示 / 指令 ，用以启动一个 全新的聊天会话 。这使得之前对话的逻辑、意图和上下文能够无缝继承到一个新阶段，通过克服上下文窗口的限制，有效地实现了与 AI 进行长期、项目式的协作。 然而，在 v1.19.0 (2026-02-11) 中，此功能被静默且彻底地改变了。摘要现在被作为一条普通的 用户消息 插入到 同一 聊天线程中。这一改动彻底削弱了该功能的实用性： 核心功能丧失： 它不再创建一个新的、可管理的聊天会话。压缩后的摘要及后续对话都被埋没在不断增长、日益冗长杂乱的现有聊天历史中，使得组织变得不可能。 工作流被破坏： 该功能的初衷——为新的讨论阶段提供一份清晰、权威的“简报”——已经消失。AI 不再将摘要视为高优先级的指令（系统提示），而仅仅是另一段上下文。 不佳的用户体验（自动触发）： 新的“在约 60% 上下文长度处自动压缩”机制具有破坏性。它粗暴地打断了深入、流畅的对话，仅仅为了节省微不足道的 Token 数量，这优先考虑了系统管理而忽视了用户的意图和创造性的思维流动。 对于从事复杂、长篇推理和项目（这是高级 AI 的一个关键优势）的用户而言，v1.18 时代的“压缩对话”不是一个“Token 节省工具”——它是一个必不可少的工作流程引擎。 强烈请求： 我强烈敦促开发与产品团队 将“压缩对话”功能回退到 v1.19 之前的逻辑，即恢复至 v1.18.x 版本所见的状态。 请恢复其生成摘要并以此作为系统提示来启动一个全新的、独立的聊天会话的能力。理想情况下，请再次将此设为默认行为，或至少将其作为一个清晰明确的用户选项提供。 当前的实现方案解决了一个对于高级用户而言不存在的（次要）问题，却摧毁了一项关键且独特的能力。感谢你们的关注。

To the Chatbox Development & Product Team, Subject: Critical Feedback on the "Compress Conversation" Feature - Request to Restore v1.18 Logic I am writing to provide feedback regarding a significant and regrettable change made to the core "Compress Conversation" function between versions v1.16.1 and v1.19.0. In v1.16.1 (2025-09-17) , you introduced the "Compress Conversation" feature. Its original and powerful implementation allowed users to generate an intelligent summary of the current dialogue, which was then used as a System Prompt / Instruction to launch a brand new chat session . This enabled seamless inheritance of the previous conversation's logic, intent, and context into a new phase, effectively allowing for long-term, project-style collaboration with the AI by overcoming context window limitations. However, in v1.19.0 (2026-02-11) , this feature was silently and fundamentally altered. The summary is now inserted as a regular User Message within the same chat thread. This change has completely neutered the feature's utility: Loss of Core Functionality: It no longer creates a new, manageable chat session. The compressed summary and subsequent dialogue are buried within the existing, increasingly long and unwieldy chat history, making organization impossible. Broken Workflow: The feature's original purpose—to provide a clean, authoritative "brief" for a new phase of discussion—is gone. The AI no longer treats the summary as a high-priority directive (system prompt) but merely as another piece of context. Poor User Experience (Automatic Trigger): The new "automatic compression" at ~60% context length is disruptive. It brutally interrupts deep, flowing conversations for marginal token savings, prioritizing system management over user intent and creative flow. For users engaged in complex, long-form reasoning and projects (a key strength of advanced AI), the v1.18-era "Compress Conversation" was not a "token saver"—it was an essential workflow engine. Strong Request: I strongly urge the development and product team to revert the "Compress Conversation" feature to its pre-v1.19 logic, as seen in v1.18.x. Please restore its ability to generate a summary and use it as a System Prompt to launch a new, distinct chat session. Ideally, make this the default behavior again, or at least provide it as a clear user option. The current implementation solves a non-existent problem (for power users) while destroying a critical, unique capability. Thank you for your consideration.