earlier part of sessions go missing sometimes

Open 💬 3 comments Opened May 10, 2026 by WilliamXXu

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

0.130.0

What subscription do you have?

plus

Which model were you using?

_No response_

What platform is your computer?

_No response_

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

the earlier part of the session went missing

What steps can reproduce the bug?

Uploaded thread: 019e128a-62b9-76c1-8c82-1b41800f29d7

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 3 months ago

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

##20303
##21635

Powered by Codex Action

etraut-openai contributor · 3 months ago

What behavior are you seeing? How do you know that the "earlier part of the session went missing"? When does this occur? Is this when you resume the session?

We recently changed the resume session path to replay the last 10K lines into the terminal's scrollback buffer. Most terminals cap their scrollback buffer at that number, so it's a waste to play back more. If you'd like to disable this optimization, you can set the value of tui.terminal_resize_reflow_max_rows to 0 in your config.toml file.

[tui]
terminal_resize_reflow_max_rows = 0

Necmttn · 2 months ago

It would help to separate transcript completeness from viewport replay.

On resume, the TUI could show loaded event counts, rendered row counts, first/last loaded turn ids, and whether a display cap is active. If the raw thread has full history but the main view renders only a slice, the UI should say showing partial replay rather than making it look like data loss.

---

_Generated with ax._