Android ChatGPT app garbles last Codex message from remote Windows machine then jumps to top of chat

Open 💬 2 comments Opened Jul 28, 2026 by ESKehler
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

When opening an existing Codex chat in the Android ChatGPT app, the last assistant/status message initially renders garbled, as if tokens/words are duplicated or interleaved. The message later corrects itself, but the view then abruptly jumps to the very top of the chat. Because there is no visible jump-to-bottom control, returning to the current message requires a long manual scroll.

Environment

  • App: ChatGPT mobile app for Android
  • Surface: Codex chat/thread view
  • Platform: Android
  • App version: 1.2026.202 (this was also happening on earlier versions of the app)
  • Seen with a long existing chat that had recent Codex status/tool activity and file-change status UI

Steps to reproduce

  1. Open the Android ChatGPT app.
  2. Open an existing long Codex chat/thread with recent assistant/status messages.
  3. Observe the most recent message immediately after the chat opens.
  4. Wait for the message to finish correcting/re-rendering.

Expected behavior

  • The latest message renders once, in the correct order.
  • The chat remains positioned near the latest content at the bottom.
  • If the view is not at the bottom, a jump-to-bottom affordance is available. (only a nice to have, especially if you find yourself all the way at the top of the chat unexpectedly)

Actual behavior

  • The latest message first appears garbled with duplicated/interleaved words, for example each word/phrase appears repeated inline.
  • After the message corrects itself, the scroll position jumps abruptly to the top of the chat.
  • On long chats this forces a long manual scroll back to the bottom.

Notes

Screenshots show the transient duplicated-word rendering and the subsequent corrected state in the Android app.

<img width="1080" height="2408" alt="Image" src="https://github.com/user-attachments/assets/615cee19-2ae6-479d-a4b0-73743f685d9e" />
<img width="1080" height="2408" alt="Image" src="https://github.com/user-attachments/assets/19544249-3b03-4fe4-961e-7ee560456f5d" />
<img width="1080" height="2408" alt="Image" src="https://github.com/user-attachments/assets/4d2fe91b-f8eb-43d8-b76a-c58167ed45b4" />

<img width="1080" height="2408" alt="Image" src="https://github.com/user-attachments/assets/0ce6649c-3098-4a42-b912-a7f2cfe7a928" />

<img width="1080" height="2408" alt="Image" src="https://github.com/user-attachments/assets/0f7c600f-4e5e-4be9-9f49-3c7dd1983433" />

<img width="1080" height="3572" alt="Image" src="https://github.com/user-attachments/assets/c440c927-a6a4-4f4f-ab4b-d7a090813aa2" />

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #35178

Powered by Codex Action

ESKehler · 29 days ago

perhaps relatedly, sometimes when i queue up messages to send remotely to codex via my computer it'll send the message but then keep it in the queue and send it again later. It seems like there are duplications or triplications of effort here