You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Add 'Jump to Answer Start' Button #9794
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
In the current development version, a "Jump to Latest" button has been added at the bottom of conversations, which is a useful feature.
However, during actual usage, I've discovered a more common use case: when AI responses are long, I often need to jump to the beginning of the current response to re-read the AI's complete answer, rather than jumping to the very bottom of the conversation.
Suggested Implementation:
Add a "Jump to Answer Start" button next to the existing "Jump to Latest" button
When clicked, the page automatically scrolls to the starting position of the current AI response
Alternatively, make the "Jump to Latest" button a smart button:
If the current position is in the middle or at the start of an AI response, the button functions as "Jump to Answer Start"
If already at the answer start, the button changes to "Jump to Latest"
Use Case Example:
AI generates a long response (containing multiple file modifications, code snippets, etc.)
User scrolls to the middle of the response to view specific content
User wants to re-understand the entire response context from the beginning
At this point, a shortcut to return to the answer start is needed, rather than manually scrolling
This feature would significantly improve the user experience when reading long responses.
Thanks for the duplicate check! I've reviewed all the suggested issues, and while they're related to navigation, none of them address this specific use case. Here's the breakdown:
That's about performance optimization and message loading for long sessions
It's a backend/infrastructure concern, not a UI navigation feature
Not related to my request
Summary: My feature request is unique - it's about quickly navigating to the beginning of the current AI response when reading long responses. This specific navigation pattern (start of current response, not top/bottom of conversation, not user messages, not manual bookmarks) isn't covered by any of the listed issues.
The use case is: AI generates a long response → I scroll down to read details → I want to quickly jump back to where the AI started this response to re-read the context → current "Jump to Latest" button doesn't help here because it takes me to the bottom, not the start of the response.
Activity
github-actions commentedon Jan 21, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
[-][FEATURE]: 添加跳转到回答开始按钮[/-][+][FEATURE]: Add 'Jump to Answer Start' Button[/+]CodeCasterX commentedon Jan 21, 2026
Thanks for the duplicate check! I've reviewed all the suggested issues, and while they're related to navigation, none of them address this specific use case. Here's the breakdown:
#5783 - Scroll down UI button when !bottom
#3337 - Navigation Shortcut to Jump Between User Messages
#9227 - Add ability to (un)mark points in the thread
#4092 - Better navigation of output, alternative vim mode
ggandGshortcuts for jumping to top/bottom of the entire conversation history#6548 - Virtualized scrolling + paginated message loading
Summary: My feature request is unique - it's about quickly navigating to the beginning of the current AI response when reading long responses. This specific navigation pattern (start of current response, not top/bottom of conversation, not user messages, not manual bookmarks) isn't covered by any of the listed issues.
The use case is: AI generates a long response → I scroll down to read details → I want to quickly jump back to where the AI started this response to re-read the context → current "Jump to Latest" button doesn't help here because it takes me to the bottom, not the start of the response.
github-actions commentedon Mar 28, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.