-
-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] 自动创建话题功能全部是默认话题了 #1926
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
好久之前就这样了 是没人发现吗? |
This happened a long time ago. Did no one notice it? |
你在设置里面关掉了吧。 设置里面可以设置,是否自动创建话题。 |
Have you turned it off in settings? You can set in the settings whether to automatically create topics. |
默认使用的是openai 的gpt-3.5 模型来的话题标题总结,如果你不添加openai 的apikey,就没法正常总结。其他用openai 的人不会遇到这个问题,可能你用的不是openai 的吧。 后续我们会做个改造,支持选择固定模型/当前会话模型进行总结,或者禁用自动总结 |
By default, the topic title summary based on openai's gpt-3.5 model is used. If you do not add openai's apikey, you will not be able to summarize normally. Other people who use openai will not encounter this problem. Maybe you are not using openai. We will make a modification in the future to support selecting fixed model/current session model for summary, or disable automatic summary. |
这我就知道了什么情况了 我用的这个key没有gpt-3.5模型的渠道 。只有gpt4相关的一些渠道 |
Now I know what's going on. The key I used does not have a channel for the gpt-3.5 model. There are only some channels related to gpt4 |
建议加个可选:不支持话题总结的话,可以摘录首个聊天的前 x 个字符作为话题标题 |
It is recommended to add an optional: If topic summary is not supported, you can excerpt the first x characters of the first chat as the topic title |
为什么不能是用当前正在使用的模型进行标题总结呢? |
Why can't we use the model currently being used for title summary? |
我想到的是,如果话题总结+当前咨询问题是一次请求的话,用模型总结是比较好的,但是如果“话题总结”跟“当前咨询问题”是分开请求的话,会比较消耗token,特别是比较长的聊天 |
What I think of is that if the topic summary + the current consultation question are one request, it is better to use the model summary, but if the "topic summary" and the "current consultation question" are requested separately, it will consume more tokens, especially when comparing long chat |
可以只对提问进行总结撒。 |
You can just summarize the questions. |
This issue is closed, If you have any questions, you can comment and reply. |
🎉 This issue has been resolved in version 0.162.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
💻 Operating System
Windows
📦 Environment
Official Preview
🌐 Browser
Chrome
🐛 Bug Description
🚦 Expected Behavior
No response
📷 Recurrence Steps
No response
📝 Additional Information
No response
The text was updated successfully, but these errors were encountered: