You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature Request: Editable session names with auto-generated titles #8436
Currently, sessions are named with a timestamp format like new session-2026-01-14-17:32. When users want to revisit previous conversations, this naming convention makes it difficult to identify specific sessions without opening each one to review its content.
In contrast, products like ChatGPT and Gemini automatically generate descriptive titles based on the conversation content (e.g., "React Hook Performance Optimization" or "Docker Compose Setup Guide"), making session history much more navigable.
Proposed Solution
Minimum Viable Feature
Editable session names: Allow users to manually rename sessions
Enhanced Feature (Recommended)
Auto-generated titles: After the user sends their first message, use the LLM to generate a concise 5-10 word title that summarizes the conversation topic
Title regeneration: Option to regenerate the title at any point during the session
Implementation Suggestions
User sends first message →
LLM generates short descriptive title →
Session is renamed automatically
The title generation could be a simple prompt like:
"Generate a concise 5-10 word title for a coding session that starts with: {first_message}"
Benefits
Faster navigation through session history
Better context at a glance
Improved user experience, especially for power users with many sessions
Feature parity with mainstream AI chat products
Additional Context
This is a common UX pattern in AI chat applications. The auto-naming significantly reduces cognitive load when managing multiple sessions.
Activity
github-actions commentedon Jan 14, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
openAgi2 commentedon Jan 14, 2026
Closing as duplicate. After investigation, I found this feature already exists and is covered by existing issues:
Apologies for the duplicate. The existing issues cover all aspects of this request.