Session loses goal-achievement metadata after Codex restart/update restart

Codex app version

26.601.20914 — released Jun 2, 2026

Platform

• macOS Tahoe 26.5
• Apple Silicon MacBook Pro
• Pro plan

Summary

Codex appears to lose some session-level detail/metadata after the app is restarted, including after an automatic restart caused by an app update.

A concrete example is the /goal result state. Before restarting Codex, a completed session showed the goal completion indicator near the bottom of the response, for example:

Goal achieved in 1h 8m 56s

After Codex restarted, the same conversation still existed, but that goal-achievement detail disappeared from the UI. The bottom of the message only showed a normal timestamp/action area, and the previous Goal achieved... label was no longer displayed.

Steps to reproduce

1. Start a Codex task using the /goal flow or a task that produces a goal-achievement status.
2. Let Codex complete the task successfully.
3. Confirm that the conversation shows a Goal achieved... completion indicator at the bottom of the completed result.
4. Restart Codex, or allow Codex to update and automatically restart.
5. Reopen the same conversation.
6. Observe that the goal-achievement indicator is no longer displayed.

Expected behavior

Session details should be preserved and rehydrated after restart, including:

• goal-achievement status,
• goal completion duration,
• task completion metadata,
• other important UI state associated with the completed session.

If a task was marked as goal-achieved before restart, the same conversation should still show that state after restart.

Actual behavior

After restart/update restart, the conversation remains visible, but some details disappear. In this case, the Goal achieved... status was lost from the UI.

Why this matters

This is not just a cosmetic issue. Goal completion state is important session metadata. Users rely on it to know whether a task was successfully completed, how long it took, and whether a conversation reached the intended target state.

Losing that detail after restart makes historical sessions less reliable and can create confusion when reviewing completed work. It also suggests that some session metadata may only be kept in transient client state instead of being persisted or correctly rehydrated after app reload.

Request

Please ensure that Codex persists and restores important session metadata across app restarts and update-triggered restarts. In particular, /goal completion state and Goal achieved... duration/status should survive a restart and remain visible when the conversation is reopened.