Codex desktop: completed replies can end hidden behind the composer instead of scrolling into view

Platform

Windows desktop app. App version not recorded.

What issue are you seeing?

After a response completes in a long Codex conversation, the viewport may preserve an older scroll position. The final lines of the completed assistant response end up below the visible area, behind or immediately above the fixed composer. The user must click the floating down-arrow or manually scroll for every response to read its ending.

This is a noticeable regression from prior behavior, where the completed reply's end was automatically visible above the composer.

Steps to reproduce

1. Open a long Codex desktop conversation.
2. Scroll to an earlier message so that the conversation has enough content to overflow the viewport.
3. Send a follow-up and wait for the assistant response to complete.
4. Observe that the reply can finish with its last paragraph obscured by the composer / outside the viewport, while a down-arrow affordance appears.

Expected behavior

When a response has completed, automatically position the viewport so that the final lines are fully visible above the composer. Alternatively, provide a user setting to restore this behavior.

Actual behavior

The response completion leaves the last lines out of view and requires an extra manual scroll or click on the down-arrow after each reply.

Why this matters

This makes ordinary conversational use unnecessarily difficult, especially for long threads. The very part of the answer that contains the conclusion, next action, or caveat is often the part hidden.

The issue names no implementation files, tests, or entry points. Start by reproducing the problem in a long Codex desktop conversation and inspect the response-completion and scrolling behavior around the fixed composer and down-arrow. Done means completed replies automatically leave their final lines fully visible above the composer without requiring a manual scroll.