Language
Problem
When reading a long conversation on the mobile client, it is easy to move far away from the latest message, including through an accidental tap or a large manual scroll. Returning to the active turn then requires a long scroll through the entire conversation.
This is especially disruptive while Codex is streaming output: the task continues at the bottom, but the user has no quick way to return to the newest content.
A scroll-to-bottom button was mentioned alongside a separate connection bug in #10, which was closed as completed for version 1.2.2. However, the current 1.4.5 mobile experience does not expose a reliable, dedicated control for returning to the latest message.
Proposal
Add a floating “scroll to latest” button to the mobile conversation view.
Suggested behavior:
- Show the button only when the user is sufficiently far from the bottom.
- Hide it after the user reaches the bottom.
- On tap, scroll directly to the latest message.
- Keep it available while a response is streaming.
- Do not force automatic scrolling while the user is intentionally reading older messages.
- Respect the bottom safe area and avoid covering the composer or message actions.
- Give the control an accessibility label such as “Scroll to latest message”.
This should use the repository's established mobile UI primitives and match the existing visual style.
Alternatives considered
Manual scrolling works for short conversations but becomes impractical for long threads. Always forcing the list to follow streaming output would make it difficult to read earlier content, so an explicit contextual button is preferable.
Language
Problem
When reading a long conversation on the mobile client, it is easy to move far away from the latest message, including through an accidental tap or a large manual scroll. Returning to the active turn then requires a long scroll through the entire conversation.
This is especially disruptive while Codex is streaming output: the task continues at the bottom, but the user has no quick way to return to the newest content.
A scroll-to-bottom button was mentioned alongside a separate connection bug in #10, which was closed as completed for version 1.2.2. However, the current 1.4.5 mobile experience does not expose a reliable, dedicated control for returning to the latest message.
Proposal
Add a floating “scroll to latest” button to the mobile conversation view.
Suggested behavior:
This should use the repository's established mobile UI primitives and match the existing visual style.
Alternatives considered
Manual scrolling works for short conversations but becomes impractical for long threads. Always forcing the list to follow streaming output would make it difficult to read earlier content, so an explicit contextual button is preferable.