[FEATURE] Customizable conversation title format
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Currently, conversation titles are auto-generated based on conversation content with no way to customize the format.
It would be useful to allow users to define a title format/template, either in CLAUDE.md, settings.json, or a dedicated configuration option.
Benefits:
- Better organization when juggling multiple tasks/tickets
- Quick cross-reference between conversations and project management tools
- Consistent naming across team members
Proposed Solution
One or more of these approaches:
- A conversationTitle instruction in CLAUDE.md or settings — e.g., a natural language instruction like:
conversationTitle: "Start with the Linear/Jira issue key if available, followed by a short description"
- A template format — e.g.:
conversationTitleFormat: "{issue_key} - {description}"
- Hook-based — a conversation_start hook that can set/override the title.
Alternative Solutions
_No response_
Priority
Low - Nice to have
Feature Category
CLI commands and flags
Use Case Example
When working on Linear/Jira tickets, I'd like conversation titles to start with the issue key followed by a brief description, e.g.:
- ENG-203 - Rspack migration
- PROJ-45 - Fix login redirect bug
This makes it much easier to find and reference past conversations when they're tied to specific tasks in a project management tool.
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗