Resume session view omits reasoning/code edits; request optional raw transcript display

Resolved 💬 4 comments Opened Feb 7, 2026 by vjain419 Closed Feb 14, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

Bug

When resuming a Codex session, the view now loads only the user messages and the final assistant output. The intermediate reasoning and code edit steps are no longer shown.

This appears to have changed recently; previously the raw session view included the full transcript (reasoning + edits), which was helpful for understanding what changed and for auditing work.

Expected

Either:

  • Restore the previous raw transcript view when resuming a session, or
  • Keep the current behavior as default but provide a config.toml option to enable the full raw transcript view (including reasoning and code edits).

Why it matters

The raw transcript makes it much easier to understand what the agent actually did, especially for code edits across multiple files or sessions.

Thank you!

View original on GitHub ↗

4 Comments

etraut-openai contributor · 6 months ago

Which variant Codex are you using? The CLI? The Extension?

I'm not aware of any change here. Are you able to pin down a particular version where this changed?

yeyaowei · 6 months ago
Which variant Codex are you using? The CLI? The Extension? I'm not aware of any change here. Are you able to pin down a particular version where this changed?

<img width="1666" height="2820" alt="Image" src="https://github.com/user-attachments/assets/4e86626c-2ef3-4c3f-ae62-804909526201" />

Hi! I just started using the Codex CLI recently and noticed this too. Maybe this is what the OP was talking about?
I created a file, edited it twice, exited the Codex session, and then resumed it. After resuming, the editing history was gone.
My codex version is codex-cli 0.98.0

vjain419 contributor · 6 months ago

Hi @etraut-openai at time of raising this I was using 0.97/0.98 either one of them and I use codex cli.
and TBH I got cron job which update codex to latest release so hard to say since which version this has been regressed.

But pretty sure at some point codex-cli was able to resume session as it is and not the way it is doing.

can you confirm if current behaviour of resume is how it design to be?

etraut-openai contributor · 6 months ago

This behavior hasn't changed. We don't store all details of the conversation in the on-disk session file, so some aspects will be missing when you restore.