Repository navigation
Saved chats reopen at incorrect scroll position instead of latest message #37291
Description
Description
When reopening a previously saved ChatGPT conversation, the conversation often loads at an incorrect position instead of the latest message.
For long conversations, this requires manually scrolling through a large history before continuing the discussion.
Steps to reproduce
- Open a long ChatGPT conversation.
- Leave the conversation.
- Reopen the saved conversation from history/sidebar.
- Observe the position where the conversation loads.
Expected behavior
Saved chats should reopen at:
- The latest message, or
- The user's last viewed position, with an easy option to jump to the newest message.
Actual behavior
The conversation opens at an arbitrary location in the history.
Impact
This creates friction for users maintaining long-running ChatGPT/Codex conversations, especially:
- Coding projects
- Research threads
- Business planning conversations
- Long-running support discussions
Environment
- ChatGPT desktop app
- macOS
- Long conversation threads
- Saved chats/history
Activity
bumbuboon commentedon Aug 20, 2026
Additional scope information:
Environment: ChatGPT Desktop 26.814.41407 (build 6720), macOS 26.5.2 (25F84).
Expected: reopen at the last viewed position or latest message.
nonohara0002 commentedon Aug 25, 2026
Additional report: scroll position lost after switching conversations — regular ChatGPT chats only
Environment: ChatGPT Desktop, version
26.814.41509, Windows 11. Only regular ChatGPT conversations are affected; ChatGPT Work is not.Steps to reproduce:
Expected behavior: returning to a conversation should restore the last scroll position. If that is not possible, it should at least open at the latest message, or provide an easy "jump to latest" affordance.
Actual behavior: every time I switch back, the conversation lands at the top or at an arbitrary old position. For long conversations, this means repeatedly scrolling through the whole history throughout the day, which is especially time-consuming when reading long replies or long lists.
Additional context: the issue only reproduces in regular ChatGPT conversations; ChatGPT Work behaves correctly. Please consider consolidating this with related reports such as #38887 and #35431.