Historical sessions lose inline execution details/tool-call history after ~1 day on macOS

What version of Codex are you using?

Latest version available as of June 2026.

What model were you using?

This does not appear to be model-specific.

What platform is your computer?

• macOS Tahoe (latest)
• MacBook Air M5

What issue are you seeing?

Immediately after a Codex session finishes, I can expand the inline execution/thread sections and inspect the commands/actions that Codex executed during the task.

However, after reopening the same session later (usually around a day later), those expandable execution details are completely gone.

The main conversation/messages are still present and intact. Only the inline execution history/tool-call/command sections disappear.

This seems specific to historical session restoration rather than the session itself being deleted.

Steps to reproduce

1. Run a task/session in the Codex macOS app using Local mode.
2. Wait for the task to finish.
3. Expand the inline execution details.
4. Observe that executed commands/actions are visible.
5. Reopen the same session the next day.
6. Observe that the expandable execution sections are no longer present at all.

Expected behavior

Historical sessions should preserve the full inline execution history, including executed commands/tool calls, even after reopening the app later.

Additional information

• Running in Local mode.
• Session data still exists locally.
• Files/changes and normal chat history are still available.
• Only the inline execution detail UI/history disappears.
• The expand arrows/inline thread controls themselves disappear entirely.

Potentially related to other session persistence/indexing issues reported in the macOS app, but this specifically affects execution trace visibility in older sessions.