What feature would you like to see?
I’d like to add a first-class session management experience in the Codex CLI that behaves similarly to how tmux handles sessions — enabling users to maintain multiple independent conversations (sessions), quickly switch between them, rename them, list them, and delete or create new ones — all from within the interactive TUI (and optionally via CLI subcommands).
Specifically:
/session — displays all saved/resumable sessions, showing metadata such as alias/name, session ID, last activity timestamp, directory/project context. It'll be interactive and the user can select to jump to a new session.
/session rename <SESSION_ID|NAME> <NEW_NAME> — assign a human-friendly alias or name to an existing session.
/session delete <SESSION_ID|NAME> — delete an existing session if no longer needed.
- Optionally mirror all of the above with CLI subcommands (e.g.,
codex session list, codex session rename …) for non-TUI workflows.
Why is this important?
- When working on multiple features/tasks/projects simultaneously, it greatly improves productivity to be able to keep multiple sessions (contexts) running side-by-side, and switch among them easily — just like tmux windows/sessions.
- While Codex CLI already supports
codex resume to pick up an old session, the workflow lacks human-friendly names/aliases, intuitive listing of sessions, and switching inside the interactive mode without dropping to shell.
- This will enable better project hygiene: easier to identify which session is for which task, organize by project, reduce cognitive overload when managing many sessions.
- A more robust session management system aligns with user expectations from other CLI agents (for example, Claude Code)
Existing related issues/discussions
While these cover parts of the session-management spectrum, none explicitly covers the full interactive in-TUI slash command workflow (/session) plus rename/delete/list/switch exactly as proposed here.
Are you interested in implementing this feature?
Yes — I’m willing and ready to contribute the implementation (forking the repo, writing tests, updating docs, submitting a PR) if the maintainers agree that this feature aligns with the roadmap and is open for review.
Thank you for considering this enhancement. I believe it will significantly improve the workflow for users managing multiple tasks/projects with Codex CLI.
Additional information
No response
What feature would you like to see?
I’d like to add a first-class session management experience in the Codex CLI that behaves similarly to how tmux handles sessions — enabling users to maintain multiple independent conversations (sessions), quickly switch between them, rename them, list them, and delete or create new ones — all from within the interactive TUI (and optionally via CLI subcommands).
Specifically:
/session— displays all saved/resumable sessions, showing metadata such as alias/name, session ID, last activity timestamp, directory/project context. It'll be interactive and the user can select to jump to a new session./session rename <SESSION_ID|NAME> <NEW_NAME>— assign a human-friendly alias or name to an existing session./session delete <SESSION_ID|NAME>— delete an existing session if no longer needed.codex session list,codex session rename …) for non-TUI workflows.Why is this important?
codex resumeto pick up an old session, the workflow lacks human-friendly names/aliases, intuitive listing of sessions, and switching inside the interactive mode without dropping to shell.Existing related issues/discussions
/session. :contentReference[oaicite:8]{index=8}While these cover parts of the session-management spectrum, none explicitly covers the full interactive in-TUI slash command workflow (
/session) plus rename/delete/list/switch exactly as proposed here.Are you interested in implementing this feature?
Yes — I’m willing and ready to contribute the implementation (forking the repo, writing tests, updating docs, submitting a PR) if the maintainers agree that this feature aligns with the roadmap and is open for review.
Thank you for considering this enhancement. I believe it will significantly improve the workflow for users managing multiple tasks/projects with Codex CLI.
Additional information
No response