Your post was moved to the appropriate place on the forum for discussing and documenting a Codex bug. The forum, however, is not the official issue tracker. If the problem needs to be formally reported and tracked by the Codex maintainers, the official place is the OpenAI Codex GitHub issue tracker.
I asked ChatGPT to search for the closest related issue, and it identified:
If that issue describes the same problem you are experiencing, consider adding a reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.
If it does not match your problem closely enough, search the existing Codex issues for a better match. If you cannot find one, consider opening a new issue and include as much relevant information as possible, such as your Codex version, operating system, environment, reproduction steps, expected behavior, actual behavior, and any relevant logs or error messages.
@EricGT, thanks for sharing the guidance and directing the report to the appropriate category.
@Emberlee, losing access to earlier output makes longer responses difficult to review. I appreciate you bringing this to our attention.
As a temporary workaround, could you try Ctrl+T to open the transcript overlay and check whether the missing content is visible there? The transcript may still be retained even when it isn’t accessible through terminal scrollback.
If that doesn’t help, email support@openai.com from the email address registered to your ChatGPT account. Include screenshots or a screen recording, your Codex CLI version, operating system version, terminal application, reproduction steps, and the workaround results.
This should be resolved with the latest release of the Codex CLI.
I created a short topic regarding this release where you can also see this feature in action.
reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.