codex - 💡(How to fix) Fix Allow users to set or rename Codex CLI session titles for easier resume [2 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#22526Fetched 2026-05-14 03:34:47
View on GitHub
Comments
2
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
commented ×2closed ×1

Root Cause

For CLI-heavy workflows, resume is one of the main ways to continue work. User-defined session names would make long-running or multi-repo work much easier to manage.

There are already related resume/thread-name issues, for example name-based resume behavior around automatically generated thread names. This request is specifically for a user-facing title/rename workflow.

Code Example

codex --name "work-pc clipimg setup"
codex rename "work-pc clipimg setup"
codex resume "work-pc clipimg setup"

---

/session rename work-pc clipimg setup
RAW_BUFFERClick to expand / collapse

Feature request

Please add a way for users to explicitly set or rename Codex CLI session titles, so sessions are easier to find later with codex resume.

Problem

When using Codex CLI frequently, the resume picker becomes hard to navigate. Thread names are currently inferred automatically, and they are not always memorable or specific enough.

This is especially painful when working across multiple repositories or when several sessions have similar first prompts. The user can resume by UUID or thread name, but there does not appear to be a clear user-facing way to assign a stable, meaningful title.

Proposed UX

Any of these would help:

codex --name "work-pc clipimg setup"
codex rename "work-pc clipimg setup"
codex resume "work-pc clipimg setup"

Or inside the TUI:

/session rename work-pc clipimg setup

Expected behavior

  • A user can set a title when starting a session.
  • A user can rename the current session later.
  • The resume picker shows the user-defined title.
  • codex resume <name> can resolve the user-defined title.
  • Renaming should avoid ambiguous or shadowed names, or make ambiguity visible in the picker.

Why this matters

For CLI-heavy workflows, resume is one of the main ways to continue work. User-defined session names would make long-running or multi-repo work much easier to manage.

There are already related resume/thread-name issues, for example name-based resume behavior around automatically generated thread names. This request is specifically for a user-facing title/rename workflow.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  • A user can set a title when starting a session.
  • A user can rename the current session later.
  • The resume picker shows the user-defined title.
  • codex resume <name> can resolve the user-defined title.
  • Renaming should avoid ambiguous or shadowed names, or make ambiguity visible in the picker.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Allow users to set or rename Codex CLI session titles for easier resume [2 comments, 1 participants]