[FEATURE] Conversation titles should be generated in the user's language
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
When conversations are conducted entirely in Korean (or other non-English languages),
Claude Code still generates sidebar conversation titles in English. This creates an
inconsistent experience where the interface language and the conversation title language
don't match. Users who work primarily in their native language have to read English
titles to identify their past conversations, which makes it harder to navigate
conversation history efficiently.
Proposed Solution
Conversation titles in the sidebar should be generated in the same language
as the conversation. If a user conducts a conversation primarily in Korean,
the title should be generated in Korean. The language detection should be
based on the language of the first few messages in the conversation.
Alternative Solutions
Currently there is no workaround. The titles are always generated in English
regardless of the conversation language, and there is no option to manually
rename conversation titles in the sidebar.
Priority
Low - Nice to have
Feature Category
Configuration and settings
Use Case Example
Example scenario:
- I start a conversation in Korean to work on my iOS app
- Claude Code automatically generates a sidebar title in English
(e.g. "Dark Mode Toggle Implementation")
- When I have many conversations, I have to read English titles
to find past Korean conversations
- If titles were generated in Korean, navigating conversation
history would be much faster and more natural
Additional Context
This affects all non-English speaking users. The conversation content
is correctly handled in the user's language, but the title generation
does not respect the conversation language. Generating the title in
the same language as the conversation would improve usability for
international users significantly.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗