Feature: Multi-Session Management for Codex CLI

[kshitizz36]

Feature: Multi-Session Management for Codex CLI

What?

Implement the ability to save, name, list, and switch between multiple Codex sessions (rollouts) from the CLI. This will make it easy for users to work on multiple projects or tasks concurrently and revisit previous sessions.

Why?

• Many users work on several projects or features at once.
• Quick context switching boosts productivity.
• Useful for demos, debugging, or reviewing past work.

How?

• Add new CLI subcommands: codex session list|save|load|delete.
• Store sessions with metadata: name, timestamp, last activity.
• Integrate with existing rollout/session logic.
• Add tests and update documentation.

Example Usage

codex session save my-new-feature
codex session list
codex session load bugfix-123
codex session delete old-session

---

[scottleibrand]

It would also be useful to include a new /session command in interactive mode that allows saving the current session/rollout.

[kshitizz36]

This is a great idea. a /session command in interactive mode, so you’ll be able to save, load, list, and delete sessions without leaving your chat.

[scottleibrand]

#118 and #146 are also asking for this, and the latter has a useful (to me) pointer to ~/.codex/sessions/rollout-*.json where sessions are already logged. Seems like the MVP here is session loading, either from the CLI or via a /session command.

[kshitizz36]

Thanks for the helpful insights! I totally agree—the MVP here is session loading, whether from the CLI or via a /session command in interactive mode, since all the necessary files are already logged in ~/.codex/sessions/rollout-*.json.

I plan to work on this once my current pending PR is merged. If anyone else wants to take a crack at these features (session loading or related session management commands), feel free to jump in—just don’t forget to give me a little credit for the idea and groundwork! 😊

[kshitizz36]

Implemented #522