-
-
Notifications
You must be signed in to change notification settings - Fork 11.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] 清空当前会话消息快捷键无响应 #4611
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
📦 Deployment environmentDocker 📌 Software versionv1.27.1 💻 System environmentWindows 🌐 BrowserChrome, Edge 🐛 Problem descriptionWhen you do not want to continue a single-round conversation, use the shortcut keys ctrl + alt + backspace. There is no response, and there is no way to clear the current conversation messages. 📷 Steps to reproduceOpen a web page and talk to any assistant 🚦 Expected resultsAbility to clear the current session's messages as before Or you can provide custom shortcut keys 📝 Supplementary informationIt seems that the shortcut keys are occupied by unknown programs |
Hello, @kindmesdilabso! I'm here to help you with any bugs, questions, or contributions. Let me know how I can assist you with the issue you've posted. I couldn't find any specific section in the codebase where the However, there is a fallback mechanism for clearing the current session if the hotkey fails. The If the hotkey conflict persists, you might consider customizing the hotkeys. The hotkeys are defined in the |
快捷键目前已删除 #4583 |
The shortcut key has been removed #4583 |
This issue is closed, If you have any questions, you can comment and reply. |
📦 部署环境
Docker
📌 软件版本
v1.27.1
💻 系统环境
Windows
🌐 浏览器
Chrome, Edge
🐛 问题描述
在单轮对话不想继续进行的时候 使用快捷键 ctrl + alt + backspace 无响应,没有办法清空当前会话消息
已经尝试了多台不同的电脑访问均无法清空当前会话消息
📷 复现步骤
打开网页,任意助手对话一句
按下 ctrl + alt + backspace 组合键
🚦 期望结果
和以前一样能够清空当前会话的消息
或者可以提供自定义快捷键
📝 补充信息
似乎快捷键被不知名程序占用
使用OpenArk查找 提示是系统的一个叫csrss.exe 的占用了这个热键
The text was updated successfully, but these errors were encountered: