[Bug] “随便聊聊”的设置未和设置页“默认助手”保持一致

[sxjeru]

📦 部署环境

Vercel

📌 软件版本

latest

💻 系统环境

Windows

🌐 浏览器

Chrome

🐛 问题描述

在“随便聊聊”中点击头像或右上角设置按钮时，会跳转“默认助手”设置页，但是“默认助手”的设置无法应用到“随便聊聊”中。

目前已知图中的几项配置肯定不会生效。

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[lobehubbot]

👀 @sxjeru

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot]

I found a similar closed issue that might be relevant to your problem. The issue discussed changes to the logic of "New Assistant" and "Casual Chat" settings. The suggested solution included:

• The menu in the upper right corner of "Casual Chat" should lead to "Conversation Settings."
• The "Conversation Settings" of "Casual Chat" should allow changes to the name and description independently from the "Default Assistant."
• "Default Assistant" should be renamed to something like "New Assistant Template" to highlight its role as a template.

For "New Assistant" or "New Conversation":

• Provide a switch in the settings to turn off the button at the top right of the list, or provide the option to set the button to "New Assistant" or "Conversation with Casual Chat."
• Change the icon of the new assistant in the upper right corner to highlight "Assistant" instead of "Conversation."

This might help address the issue of settings not being applied as expected ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[arvinxx]

随便聊聊的设置页会在新 db 方案全量迁移后（预计本月底左右）修正掉。目前由于存在新旧 db 方案不兼容问题，因此这个不太好改。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

The setting page of the casual chat will be corrected after the new DB solution is migrated (expected to be around the end of this month). At present, due to the incompatibility of the new and old DB solutions, this is not easy to change.