-
Notifications
You must be signed in to change notification settings - Fork 2.6k
feat: use Ctrl/Cmd + ↑/↓ to navigate message history #1501
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
feat: use Ctrl/Cmd + ↑/↓ to navigate message history #1501
Conversation
| handleSubmit: (e: React.FormEvent) => void; | ||
| isLoading?: boolean; | ||
| onStop?: () => void; | ||
| commandHistory?: string[]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we want to maintain a fixed size array?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @yingjiehe-xyz , what do you mean a "fixed size array"? In JavaScript the array size is not fixed.
Or are you suggesting the max size of the array for performance consideration? I think that is not necessary here too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry for the confusing, yes, the max size for history, I think so, not too many messages right now
yingjiehe-xyz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
|
Hi @yingjiehe-xyz would you merge this PR? I don't see the merge button here. Thanks |
oh, I thought you could merge it, my bad |
* main: bugfix: refactor workdirs to be async-safe, and simpler (#1558) feat: split required_extensions in bench to builtin/external (#1547) fix: continue to use resumed session after confirmation is cancelled (#1548) feat: add image tool to developer mcp (#1515) docs: using gooseignore (#1554) ci: use cargo update --workspace to ensure Cargo.lock is updated (#1539) fix: respond to interrupted tool calls with a ToolResponseMessageContent (#1557) fix: get tool def back to chat mode (#1538) ui: add default icon (#1553) fix: fix summarize agent, use session_id and add provider fn (#1552) feat(agent): memory condensation for longer context (#1457) docs: goose tips blog (#1550) docs: update to provider view (#1546) docs: resuming sessions (#1543) feat: goose bench framework for functional and regression testing feat: use refresh_tokens from databricks api (#1517) feat: use Ctrl/Cmd + ↑/↓ to navigate message history (#1501) feat: remove tools from chat mode (#1533) feat: use dropdown for goose selection (#1531) docs: goosehints in desktop (#1529)
This PR is to implement the feature request in issue.
We decide to implement the
Ctrl/Cmd + ↑/↓option to navigate through the history message.Screen.Recording.2025-03-04.at.3.59.33.PM-1.mov