CLI: rename threads directly from the /resume picker
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
Codex CLI (TUI)
What feature would you like to see?
Allow users to rename a selected thread directly from the /resume picker, without first resuming that thread.
Suggested interaction:
- Open
/resume. - Highlight an active thread.
- Press a shortcut such as
Ctrl+R. - Edit the current thread name in an inline, prefilled editor.
- Press Enter to save or Escape to cancel.
After a successful rename, the picker should update the row and reapply the current search filter while keeping the renamed thread selected when possible. Empty names should be rejected with an inline message, and save failures should leave the editor open so the user can retry.
This would make it much faster to organize a long thread list. The existing /rename command works after opening a thread, but cleaning up several entries currently requires repeatedly resuming a thread, renaming it, and returning to the picker. Renaming in place avoids changing the active context merely to perform list maintenance.
Additional information
This is a focused follow-up to #4163 and #4727. Issue #4163 was completed by adding /rename and displaying names in the resume list; #4727 was closed as a duplicate of it. The remaining request is specifically the ability to rename a different thread from the picker itself.
The app-server already exposes thread/name/set, and the picker already has the selected thread ID, so this should not require a new persistence format or protocol method. A custom keybinding that already claims Ctrl+R should continue to take precedence. Archived threads could remain read-only until restored if the rename API intentionally excludes archived threads.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the /resume picker and the existing /rename command flow, then trace how the selected thread ID is passed to the app-server's thread/name/set endpoint. Confirm how custom Ctrl+R bindings and archived threads are handled. Done means an inline editor can save or cancel, rejects empty names, keeps the picker selection when possible, reapplies its filter, and leaves failed saves retryable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100