Bug: Search keeps jumping back to first result when Codex updates while scrolling
What version of the Codex App are you using (From “About Codex” dialog)?
26.623.70822
What subscription do you have?
Plus
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
When using search inside Codex and scrolling through the results/conversation, the view unexpectedly jumps back to the first search result whenever Codex starts thinking, writes a new update, or changes the output.
This interrupts the user flow because it becomes difficult to continue reading or reviewing later search matches. Instead of staying at the current scroll position or the currently selected search result, the UI resets/jumps back to the first match.
What steps can reproduce the bug?
- Open a Codex conversation or task with enough content to scroll.
- Use the search function and search for any term that appears multiple times.
- Scroll down to a later search result or continue reading below the first result.
- Let Codex continue thinking, writing, or updating the task output.
- Observe that the view jumps back to the first search result.
What is the expected behavior?
The UI should keep the current scroll position or the currently selected search result while Codex continues thinking or writing.
Search should not automatically reset the viewport to the first result unless the user explicitly selects it.
Additional information
Whenever Codex updates the output, the page jumps back to the first search result, causing the user to lose their place.
Actual behavior
Whenever Codex updates the output, the page jumps back to the first search result, causing the user to lose their place.
Impact
This makes it hard to review search results in longer Codex sessions, especially when Codex is still actively working. It breaks reading flow and forces the user to manually scroll back to the previous position repeatedly.
Suggested fix
Preserve the active search result index and scroll position during live updates. Codex output updates should not trigger a search-navigation reset unless the search query changes or the user manually navigates to another result.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗