What feature would you like to see?
Summary
Add the ability for users to manually set or rename a session title, making it easier to identify and org
anize sessions in the /sessions list.
Motivation / Use Case
Currently, session titles are automatically extracted from conversation content by analyzing wire.jsonl
. While this works for simple cases, it has several limitations:
-
Non-descriptive titles: Auto-generated titles may not accurately reflect the session's purpose, es
pecially when the conversation starts with vague queries or code snippets.
-
Multiple related sessions: When working on different aspects of the same project (e.g., "Login Fea
ture - Backend" vs "Login Feature - Frontend"), auto-generated titles may be too similar to distinguish.
-
Long-term organization: Users who maintain sessions over days or weeks need meaningful names to qu
ickly resume the right context.
-
Consistency with other tools: Most chat/IDE tools (ChatGPT, Claude, Cursor, etc.) allow users to r
ename conversations for better organization.
Proposed Solution
Option 1: /rename Slash Command (Recommended)
Add a new slash command /rename (or restore /title):
─────────────────────────────────────────────────────────────────────────────────────────────────────────
Thank you for considering this feature! I'm happy to provide more details or discuss implementation appro
aches.
Additional information
No response
What feature would you like to see?
Summary
Add the ability for users to manually set or rename a session title, making it easier to identify and org
anize sessions in the
/sessionslist.Motivation / Use Case
Currently, session titles are automatically extracted from conversation content by analyzing
wire.jsonl. While this works for simple cases, it has several limitations:
Non-descriptive titles: Auto-generated titles may not accurately reflect the session's purpose, es
pecially when the conversation starts with vague queries or code snippets.
Multiple related sessions: When working on different aspects of the same project (e.g., "Login Fea
ture - Backend" vs "Login Feature - Frontend"), auto-generated titles may be too similar to distinguish.
Long-term organization: Users who maintain sessions over days or weeks need meaningful names to qu
ickly resume the right context.
Consistency with other tools: Most chat/IDE tools (ChatGPT, Claude, Cursor, etc.) allow users to r
ename conversations for better organization.
Proposed Solution
Option 1:
/renameSlash Command (Recommended)Add a new slash command
/rename(or restore/title):─────────────────────────────────────────────────────────────────────────────────────────────────────────
Thank you for considering this feature! I'm happy to provide more details or discuss implementation appro
aches.
Additional information
No response