Saved chats reopen at incorrect scroll position instead of latest message

Open
#37,292 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos
Domain
desktop

Research direction

Start by reproducing the issue in the ChatGPT desktop app on macOS with a long saved conversation, following the listed steps. Investigate the conversation reopen and scroll-restoration entry point; done means reopening consistently shows the latest message or preserves the last viewed position with an easy way to reach the newest message.

Written by the indexing model from the issue text.

Description

app bug session

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

  1. Open a long ChatGPT conversation.
  2. Leave the conversation.
  3. Reopen the saved conversation from history/sidebar.
  4. 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
Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.