TUI resume main view shows partial transcript when `terminal_resize_reflow_max_rows` is capped
What version of Codex CLI is running?
0.129.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.5
What platform is your computer?
Darwin 23.6.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
zsh/oh-my-zsh
What issue are you seeing?
When resuming a long TUI session, the main resumed view can show only a partial transcript, making it look like most of the session history was lost.
In my case, thread/resume returns the full session history and Ctrl+T opens the full transcript, so the data is loaded correctly; however, the normal main TUI view after codex resume only shows the first prompt/partial history.
The issue appears tied to tui.terminal_resize_reflow_max_rows. Setting tui.terminal_resize_reflow_max_rows=0 makes the full transcript appear in the main resumed view.
What steps can reproduce the bug?
- Have a long Codex session with more transcript rows than the resize-reflow row cap.
- Resume it with default TUI settings.
- Main TUI view shows only an early/partial portion of the transcript, making history appear missing.
- Press Ctrl+T and the full transcript is present.
- Resume with
-c tui.terminal_resize_reflow_max_rows=0and the full transcript appears in the main view.
What is the expected behavior?
After codex resume, the main TUI view should not make the transcript appear lost or truncated when the full transcript is available.
If row-capping is applied during initial replay, the UI should either show the most useful recent tail of the transcript, clearly indicate that older transcript rows were omitted from the main terminal scrollback buffer, or otherwise keep the main view consistent with the full transcript available through Ctrl+T.
Additional information
thread/resumereturns all turns for the session, so persistence/resume loading is correct.- The issue appears isolated to initial history replay / resize-reflow row cap in the main TUI scrollback.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗