Codex Desktop navigation rail positions the selected user turn near the bottom instead of the top

What version of the Codex App are you using (From “About Codex” dialog)?

26.730.61639 (6234)

What subscription do you have?

Not specified. This appears to be a desktop transcript navigation/positioning issue rather than plan-specific behavior.

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

In a long Codex task thread, clicking a turn marker in the compact navigation rail on the left smoothly scrolls to the selected user turn, but the selected user message is positioned near the bottom of the viewport.

This makes the jump feel incomplete because the assistant response associated with that user message remains mostly below the viewport. I need to scroll manually again before I can read the selected turn.

The animation itself appears to work; the problem is the final scroll alignment. It looks as if the target is using bottom/nearest alignment instead of start/top alignment.

What steps can reproduce the bug?

1. Open a sufficiently long Codex task thread in the unified ChatGPT desktop app.
2. Hover over the compact conversation navigation rail on the left side of the transcript.
3. Click a marker for an earlier user turn.
4. Wait for the smooth-scroll animation to finish.
5. Observe that the selected user message lands near the bottom of the viewport, close to the composer, rather than near the top.

What is the expected behavior?

After selecting a marker, the corresponding user message should land near the top of the transcript viewport, with a small offset for the app header if necessary.

This would leave the associated assistant response visible below the prompt and make the selected turn readable without requiring a second manual scroll.

The intended behavior is similar to structured document navigation: one click should place the selected section at the beginning of the readable area.

Additional information

This is distinct from reports about the navigation rail being missing or its markers disappearing. The rail is visible and clickable; only the final target alignment feels incorrect.

Related design discussions:

• #35975 asks for navigation anchors to jump to the exact user-message boundary and track the turn nearest the top of the viewport.
• #11849, although for the VS Code extension and keyboard navigation, explicitly proposes positioning the selected user message at the top of the viewport.
• #32015 concerns visibility of the existing conversation navigation markers, not click alignment.