Cmd. /rename
Rename the current saved Codex chat without changing its transcript or execution state.
Key takeaways
- Rename the current saved Codex chat without changing its transcript or execution state.
- Check the input surface and availability before using the examples below.
Purpose
Rename the current saved Codex chat without changing its transcript or execution state.
/rename [name]Availability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
The installed command menu and account or organization settings determine availability.
Examples
/rename parser-migrationWhen to use it
- Run
/rename AUTH-241 refresh-token raceto record the issue and purpose. - Run
/renamewithout arguments and edit the suggested title to match the team convention.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/rename | Renames the current chat | Existing work needs a searchable name |
/new [name] | Creates and names a new chat | You need a fresh context |
/title | Configures the terminal window title | You need to distinguish OS windows or tabs |
Effects and persistence
Changes the current session's name while retaining its conversation.
/rename [name] updates the saved name of the current chat without changing its transcript.
Cautions
- Renaming does not change the transcript or Git branch.
- Do not put secrets, customer data, or tokens in chat names.
- Prefer a short searchable prefix over a long description.
- Unnamed tasks receive automatic titles in 0.150.0+, but durable work should still use a reviewed team-readable name.
Official sources
Complete command list · Verification scope · History for this command