Do not jump to bottom when sending follow-up while scrolled up in a thread

Summary

Codex Desktop on macOS jumps to the bottom of the current thread when I send a follow-up message while I am scrolled up reading older content. This makes it easy to lose my place in long conversations.

Environment

• Codex App version: 26.305.950 (build 863)
• Platform: macOS 15.7.3
• Architecture: Apple Silicon / arm64

Steps to reproduce

1. Open an existing thread with enough content to scroll.
2. Scroll up into older parts of the conversation and start reading.
3. Type a follow-up prompt in the composer.
4. Send the follow-up.

Actual behavior

The view jumps to the bottom of the thread, so the previous reading position is lost.

Expected behavior

One of these would be much better:

• Preserve the current scroll position after sending the follow-up.
• If auto-jump is intentional, provide a setting to control it.
• Offer a "return to my previous spot" affordance after the new message is sent.

Why this is disruptive

In long threads, I often want to keep reading earlier output while sending a short follow-up. The current behavior interrupts that flow and forces me to manually find my place again.

Notes

• I could not find a documented config.toml setting for this behavior.
• I also could not find a clearly matching open GitHub issue for this exact follow-up-scroll case in the desktop app.