Codex App find-in-thread result keeps re-anchoring viewport during active conversation

Resolved 💬 2 comments Opened Jul 3, 2026 by Sungyoun-Kim Closed Jul 3, 2026

What issue are you seeing?

In a long Codex App thread, after using Cmd+F / Find in thread to jump to an older match, the thread viewport keeps returning to that find result while the conversation continues.

I can manually scroll back down to the latest conversation/output, but when new assistant output is generated or the thread re-renders, the viewport jumps back to the old find-result location again. This makes it difficult to follow the latest messages in an active thread.

This looks like a stale find-result scroll anchor being reapplied during active output rendering or transcript updates.

What steps can reproduce the bug?

  1. Open a long Codex App thread.
  2. Press Cmd+F and search for text that appears in an older message.
  3. Let the viewport jump to the matched result.
  4. Manually scroll back down to the latest conversation/output.
  5. Continue the conversation while the assistant is generating or while the thread is updating.
  6. Observe that the viewport repeatedly returns to the older find-result location instead of staying near the latest output.

What is the expected behavior?

After the user manually scrolls away from a find result, the app should not keep forcing the viewport back to that stale find anchor during subsequent conversation updates.

If the user is following the latest output, the thread should remain near the latest messages unless the user explicitly invokes find navigation again.

Additional information

Platform observed: macOS Codex App.

No response.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗