Let Codex rename the current thread when explicitly asked
Open 💬 5 comments Opened Mar 22, 2026 by taxijjang
What variant of Codex are you using?
App
What feature would you like to see?
I'd like Codex to rename the current thread when I explicitly ask in natural language, for example:
- "rename this thread to checkout rollback follow-up"
- "change this chat title to MCP investigation"
Today I have to remember and type /rename ... manually.
Proposed behavior:
- expose a current-thread-scoped action/tool the assistant can invoke
- only use it when the user explicitly asks to rename the current thread
- if the user asks to rename the thread but does not provide a name, ask a short follow-up question
- reuse the existing thread rename path instead of adding a separate workflow
This would make thread naming feel like a normal assistant action instead of a slash-command-only workflow.
Additional information
I found related issues, but they seem broader or different:
- CLI-1556 is broader session management
- CLI-205 was about named sessions more generally and is closed
I also looked through the code locally and found existing rename plumbing already in place (/rename, an app-server thread/name/set request, and persisted thread-name updates). This request is specifically about making that functionality assistant-invokable for the current thread.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗