/experimental shows redundant "Memories will be enabled in the next session" warning when Memories is already enabled

Resolved 💬 1 comment Opened Apr 19, 2026 by ghost Closed Apr 19, 2026

What version of Codex CLI is running?

codex-cli 0.122.0-alpha.10

What subscription do you have?

ChatGPT Pro

Which model were you using?

gpt-5.4 xhigh

What platform is your computer?

Darwin 25.2.0 arm64 arm

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

Ghostty 1.3.1

What issue are you seeing?

When I open /experimental, the Memories checkbox is already checked. If I press Enter immediately without changing anything, Codex adds the warning Memories will be enabled in the next session.

That warning looks redundant in this case. Memories were already enabled for the current session, and I did not change the checkbox state.

What steps can reproduce the bug?

  1. Start a Codex CLI session where Memories is already enabled.
  2. Run /experimental.
  3. Confirm that [x] Memories is already checked.
  4. Press Enter without toggling any options.
  5. Observe the warning Memories will be enabled in the next session.

What is the expected behavior?

No warning should appear on a no-op save.

The warning should only appear if Memories actually transitions from disabled to enabled and a new session is required for that change to take effect.

Additional information

This looks like the /experimental save path may be submitting the full feature snapshot, and the notice may be keyed off Feature::MemoryTool = true instead of an actual disabled-to-enabled transition.

The code path that seems most relevant is:

  • codex-rs/tui/src/bottom_pane/experimental_features_view.rs
  • codex-rs/tui/src/app.rs
  • codex-rs/tui/src/chatwidget.rs

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗