codex - 💡(How to fix) Fix Make Codex memory writability explicit when `memories = true` is enabled [1 comments, 2 participants]

What feature would you like to see?

When the memories feature is enabled, Codex should make memory writability explicit and non-contradictory.

Right now, a direct codex launch can show memories enabled in config/features, while the model-visible prompt still injects:

Never update memories. You can only read them.

From a user perspective, that is extremely confusing. It makes the feature appear enabled but unusable.

What problem is this solving?

This creates a bad UX for users who rely on durable memory and are trying to understand whether memory is:

• enabled
• experimental
• readable only
• writable
• intentionally disabled by policy in the current session

At the moment, users can spend a lot of time checking local config and launchers before discovering that the effective behavior is controlled by an injected prompt/policy.

Suggested improvements

Any of these would be a big improvement:

1. Add a clear session-visible status for memory mode, such as:

   • memory: disabled
   • memory: read-only
   • memory: writable

2. If memories = true is enabled but writes are blocked by policy, show that clearly in the CLI/UI instead of only via hidden prompt instructions.

3. Document the difference between:

   • enabling the memory feature in config
   • actual write permission in the active session

4. If read-only memory is intentional for now, expose that as a visible product state instead of making users discover it through debug prompt-input.

5. Ideally, provide a real toggle or future supported mode for writable durable memory when the product is ready.

Additional context

Confirmed locally on a plain direct codex launch:

• Codex CLI: 0.123.0
• Subscription: ChatGPT Plus
• Platform: Linux ARM64 (Raspberry Pi)
• ~/.codex/config.toml has memories = true
• codex features list shows memories enabled
• codex debug prompt-input "test" still shows the injected line: Never update memories. You can only read them.

I’m not asserting that writable memory must exist today. The core request is that Codex should make the effective memory mode obvious and avoid the current contradictory UX.