Feature request: Optional cross-session memory / project memory in Codex

What happened

I’m using Codex across multiple sessions/folders. Each new session starts with no memory of prior context, decisions, or project status.

Thread ID with uploaded context:
019c9f67-efb0-76b1-8c30-713aa5da2572

## What I expected
An optional cross-session memory system so Codex can remember relevant project context between sessions (with user control).

## Why this matters
Without memory, I have to re-explain:

• project goals
• current architecture decisions
• tooling setup
• pending tasks / next steps

This slows down iteration and increases mistakes.

## Requested feature
Please add opt-in cross-session memory with clear controls:

1. Per-project memory namespace (not global by default)
2. User-approved memory writes
3. View/edit/delete saved memory
4. TTL/expiration options
5. “Use memory for this session” toggle
6. Ability to import from prior thread IDs

## Minimum viable version
Even a lightweight “Project Memory” file managed by Codex automatically (with explicit approval) would help a lot.

## Environment

• Codex CLI
• Multiple local project folders