Skip to content
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

[Feature Request] 希望保留重试历史,而不是直接覆盖旧的回答 #6258

Open
efJerryYang opened this issue Feb 19, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@efJerryYang
Copy link

🥰 需求描述

#5439 这个 issue 其实提到了这个问题,但提出人关闭了对应的 issue 然后仅尝试解决另外一个问题。

在 ChatGPT 中,当用户点击重试时,会产生多个回答记录可供切换,而并非 ChatGPTNextWeb 中的覆盖原来的回答.

这个 feature 是确实有需求的,因为有时候(尤其是 DeepSeek )我对回答不满意想要重试时,结果重试的结果是 Error 直接导致原来的回答丢失,这样非常不方便。

🧐 解决方案

通过界面的按钮重试时,希望能保留旧历史,类似于 ChatGPT 和 Claude 的网页端支持的功能,能够在不同的回复历史中进行浏览,组织成不同的回答链。可能需要对历史的组织逻辑进行重构,但我认为这个确实是一个必要的 feature request 。

📝 补充信息

No response

@efJerryYang efJerryYang added the enhancement New feature or request label Feb 19, 2025
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Title: [Feature Request] Want to keep the retry history instead of overwriting the old answer directly

🥰 Requirement description

#5439 This issue actually mentioned this issue, but the proposer closed the corresponding issue and then tried to solve another issue.

In ChatGPT, when the user clicks to try again, multiple answer records are generated to switch, rather than overriding the original answer in ChatGPTNextWeb.

This feature is indeed in demand, because sometimes (especially DeepSeek) when I am not satisfied with the answer and want to try again, the result of the retry is that the Error directly leads to the loss of the original answer, which is very inconvenient.

🧐 Solution

When retrying through the buttons in the interface, I hope to preserve the old history. Similar to the functions supported by ChatGPT and Claude on the web page, it can browse in different replies history and organize into different replies chains. The organizational logic of history may need to be refactored, but I think this is indeed a necessary feature request.

📝 Supplementary information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants