Problem or Motivation
When working with multiple sessions, the only way to identify a session is by its auto-generated UUID (e.g., 4518f874-0c83-4e0e-a0da-043000c4a46a) or the truncated first/last prompt text shown in the /resume picker. This makes it difficult to quickly locate and switch between sessions, especially when working on multiple tasks across interleaved deployments.
Tools like Codex and Claude Code support renaming sessions to give them human-readable names, which greatly improves session management UX.
Related: #59
Proposed Solution
Add a /rename slash command that allows users to rename the current session with a custom title.
Usage 1: Inline rename
Directly provide the new name as an argument:
> /rename deploy-fix-prod
Session renamed to: deploy-fix-prod
Usage 2: Interactive rename
When no argument is provided, prompt the user to enter a new name:
> /rename
Enter new session name: deploy-fix-prod
Session renamed to: deploy-fix-prod
After renaming, the custom name should be visible in:
- The welcome banner when resuming the session
- The exit message alongside the resume command
- The
/resume session picker
Alternatives Considered
/name command: Functionally identical; /rename is preferred as it aligns with the verb used by Codex and Claude Code, and is more intuitive (you're renaming an existing session, not naming a new one).- Auto-generated names from first prompt: Already partially implemented via
first_prompt in the session index, but auto-titles are often too long or not meaningful enough for quick identification.
Related Area
CLI / Interactive Mode
Additional Context
This is a subset of the broader session management improvements discussed in #59.
Problem or Motivation
When working with multiple sessions, the only way to identify a session is by its auto-generated UUID (e.g.,
4518f874-0c83-4e0e-a0da-043000c4a46a) or the truncated first/last prompt text shown in the/resumepicker. This makes it difficult to quickly locate and switch between sessions, especially when working on multiple tasks across interleaved deployments.Tools like Codex and Claude Code support renaming sessions to give them human-readable names, which greatly improves session management UX.
Related: #59
Proposed Solution
Add a
/renameslash command that allows users to rename the current session with a custom title.Usage 1: Inline rename
Directly provide the new name as an argument:
Usage 2: Interactive rename
When no argument is provided, prompt the user to enter a new name:
After renaming, the custom name should be visible in:
/resumesession pickerAlternatives Considered
/namecommand: Functionally identical;/renameis preferred as it aligns with the verb used by Codex and Claude Code, and is more intuitive (you're renaming an existing session, not naming a new one).first_promptin the session index, but auto-titles are often too long or not meaningful enough for quick identification.Related Area
CLI / Interactive Mode
Additional Context
This is a subset of the broader session management improvements discussed in #59.