-
-
Notifications
You must be signed in to change notification settings - Fork 11.5k
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
[Request] 上下文发送复选框和消息展开收起按钮 #5715
Comments
👀 @wwwedf1 Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
🥰 Demand descriptionAt present, the most efficient way to manage the context sent to AI is the topic of sub -topics and creating a copy. If you want to prevent a message from being sent to the API as the context in a conversation, one method is to find the previous user message and click that position to generate it. All the messages after this user message will not be sent as context. If you click on the AI response to the re -generation instead of re -generating and deleting, it seems that the previous reconnectional reply is sent as context. AI sometimes ignores the context sent such, but sometimes it seems that thinking is still affected by the context sent such. Thoroughly deleting a message can manage the context, but it is very inconvenient, it is difficult to do if there is what you want. 🧐 SolutionAdd this message to the check box sent by the context when each message is added when the next user prompts. Add a folding message button at the same time to facilitate the index. 📝 Supplement information_NO Response |
最好的做法应该还是像chatgpt那样做分支的效果,这个准备做的 |
The best way is to make a branch like ChatGPT. |
🥰 需求描述
目前管理发送给ai的上下文的最高效方式是子话题和创建副本。如果在一个对话中想要防止某条消息被作为上下文发送给api,一个方法是找到其上一条用户消息点击那个位置的重新生成,这条用户消息之后的所有消息都不会作为上下文被发送。如果点击ai回应处的重新生成而不是重新生成并删除,似乎会把之前重新生成的回复作为上下文发送。ai有时会忽略这样发送的上下文,但是有时似乎思维仍然会受到这样发送的上下文影响。彻底删除某条消息可以管理上下文,但是很不方便,万一里面有想要的就很难办。
🧐 解决方案
在每条消息处增加是否在发送下一条用户提示时将本条消息拼接进上下文发送的复选框。同时添加折叠消息按钮,便于索引。
📝 补充信息
No response
The text was updated successfully, but these errors were encountered: