Is your feature request related to a problem?
Yes. Currently, conversations in Qwen Code are identified only by UUIDs (e.g., 8a1af242-9852-42a9-9580-cfc682adec7e). When users need to revisit a specific conversation (e.g., a debugging session from 2 weeks ago), they have no intuitive way to find it without manually searching through file metadata or content.
Describe the solution you'd like
I'd like to see one or more of the following features:
-
Automatic conversation titles: Qwen could auto-generate a short descriptive title based on the first user message (e.g., "Twilio video debugging - audio issues", "Patient registration flow", "Mobile responsiveness fixes").
-
Manual conversation naming: Allow users to name/tag conversations via a command like /rename "Twilio video bugs" or /tag "feature:video-calls".
-
Conversation index/sidebar: A searchable sidebar or index file that lists conversations with their auto-generated or manual titles, dates, and sizes.
-
Search by topic: Ability to search past conversations by keyword (e.g., "twilio", "video_session.js", "debugging").
Describe alternatives you've considered
- Manually maintaining an index file (
.qwen/CONVERSATION_INDEX.md) with conversation IDs and descriptions. This is error-prone and requires extra effort.
- Searching through conversation files by content using grep. This is slow and requires technical knowledge.
Additional context
We recently spent considerable time trying to find a specific conversation about Twilio video debugging. The conversation had ~40% context usage with large console logs, but was only identifiable by its UUID. Having titles or tags would have saved significant time.
Is your feature request related to a problem?
Yes. Currently, conversations in Qwen Code are identified only by UUIDs (e.g.,
8a1af242-9852-42a9-9580-cfc682adec7e). When users need to revisit a specific conversation (e.g., a debugging session from 2 weeks ago), they have no intuitive way to find it without manually searching through file metadata or content.Describe the solution you'd like
I'd like to see one or more of the following features:
Automatic conversation titles: Qwen could auto-generate a short descriptive title based on the first user message (e.g., "Twilio video debugging - audio issues", "Patient registration flow", "Mobile responsiveness fixes").
Manual conversation naming: Allow users to name/tag conversations via a command like
/rename "Twilio video bugs"or/tag "feature:video-calls".Conversation index/sidebar: A searchable sidebar or index file that lists conversations with their auto-generated or manual titles, dates, and sizes.
Search by topic: Ability to search past conversations by keyword (e.g., "twilio", "video_session.js", "debugging").
Describe alternatives you've considered
.qwen/CONVERSATION_INDEX.md) with conversation IDs and descriptions. This is error-prone and requires extra effort.Additional context
We recently spent considerable time trying to find a specific conversation about Twilio video debugging. The conversation had ~40% context usage with large console logs, but was only identifiable by its UUID. Having titles or tags would have saved significant time.