feat: session persistence

Resolved 💬 5 comments Opened Apr 16, 2025 by yuan-alex Closed Aug 7, 2025

Allow the user to continue a previously saved session/thread with the same current working directory by using a command like /session. This command can only be used before any message has been sent.

Incremental thread state is already persisted in ~/.codex/sessions/rollout-*.json but an alternative structure is necessary to store thread information.

A simple alternative could allow the user to continue the most recently saved thread state for the current working directory.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗