Summary
Add rename button for sessions.
Problem to solve
It would be useful to have a visible Rename Session action in the UI.
Right now, renaming a session requires CLI/API access, which is fine for power users but awkward for normal day-to-day organization.
A simple rename action in the session header or session list would make it much easier to manage long-running conversations and multi-topic threads, and would help organize sessions much better.
Proposed solution
Suggested behavior:
allow editing the session label directly from the UI
keep it lightweight and optional
preserve the current session key; only change the display label
This seems like a small UX improvement that would save time and reduce clutter.
Alternatives considered
Keeping session renaming limited to CLI/API only. This works for power users, but it is inconvenient for everyday use and slows down session organization.
Relying on automatically generated session titles. This helps initially, but it does not address cases where users want to add clearer, custom names for long-running or multi-topic conversations.
Adding a separate tagging system instead of renaming. That could help with organization, but it would be a heavier change and would not solve the basic need for a simple editable session label.
Impact
Impact: This would improve session organization and make it easier to manage long-running or multi-topic conversations. It would also reduce clutter in the session list and remove the need to use CLI/API just to rename sessions.
Better session organization
Faster day-to-day workflow
Less clutter in long-running chats
Easier to identify and revisit topics
Reduced need to use CLI/API for a simple UI task
Evidence/examples
Unmeaningful defalt names.
Summary
Add rename button for sessions.
Problem to solve
It would be useful to have a visible Rename Session action in the UI.
Right now, renaming a session requires CLI/API access, which is fine for power users but awkward for normal day-to-day organization.
A simple rename action in the session header or session list would make it much easier to manage long-running conversations and multi-topic threads, and would help organize sessions much better.
Proposed solution
Suggested behavior:
allow editing the session label directly from the UI
keep it lightweight and optional
preserve the current session key; only change the display label
This seems like a small UX improvement that would save time and reduce clutter.
Alternatives considered
Keeping session renaming limited to CLI/API only. This works for power users, but it is inconvenient for everyday use and slows down session organization.
Relying on automatically generated session titles. This helps initially, but it does not address cases where users want to add clearer, custom names for long-running or multi-topic conversations.
Adding a separate tagging system instead of renaming. That could help with organization, but it would be a heavier change and would not solve the basic need for a simple editable session label.
Impact
Impact: This would improve session organization and make it easier to manage long-running or multi-topic conversations. It would also reduce clutter in the session list and remove the need to use CLI/API just to rename sessions.
Better session organization
Faster day-to-day workflow
Less clutter in long-running chats
Easier to identify and revisit topics
Reduced need to use CLI/API for a simple UI task
Evidence/examples
Unmeaningful defalt names.
