Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] Option to configure language for auto-generated session history titles [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54937•Fetched 2026-05-01 05:50:32
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
ryu0328to-cmykryu0328to-cmyk
Participants
github-actions[bot]github-actions[bot]ryu0328to-cmykryu0328to-cmyk
Timeline (top)
labeled ×3closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Session history titles are auto-generated in English regardless of the user's language. For non-English users (e.g., Japanese users), all session titles appear in English even when the conversation is conducted entirely in another language. This makes it difficult to quickly identify sessions at a glance.

Proposed Solution

Add a setting (e.g., in Claude Code settings or settings.json) to configure the preferred language for auto-generated session history titles. When set, titles should be generated in the specified language regardless of the interface language.

Example: "sessionTitleLanguage": "ja" would generate titles in Japanese.

Alternative Solutions

Currently, starting conversations in the target language sometimes influences the title language, but this is inconsistent and not reliable. There is no way to guarantee titles appear in a specific language.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

  1. User is a Japanese speaker who uses Claude Code entirely in Japanese.
    1. All session history titles appear in English (e.g., "Build random Pokemon display website").
    1. The user wants titles to appear in Japanese (e.g., "ランダムポケモン表示サイト構築") for easier navigation.
    1. With this feature, setting "sessionTitleLanguage": "ja" in settings.json would automatically generate Japanese titles.

Additional Context

No response

extent analysis

TL;DR

Implementing a setting to configure the preferred language for auto-generated session history titles would allow users to view titles in their native language.

Guidance

  • Introduce a new setting, such as "sessionTitleLanguage", in the application's settings or settings.json to store the user's preferred language for session titles.
  • Update the session title generation logic to use the specified language when generating titles, if set.
  • Consider adding a fallback mechanism to handle cases where the specified language is not supported or the setting is not configured.
  • Test the new feature with different languages, including Japanese, to ensure correct title generation.

Example

{
  "sessionTitleLanguage": "ja"
}

This example shows how the new setting could be configured in settings.json to generate session titles in Japanese.

Notes

The implementation details may vary depending on the application's architecture and existing internationalization mechanisms. This solution assumes that the application already supports multiple languages and has the necessary infrastructure for generating titles in different languages.

Recommendation

Apply workaround: Implement the proposed solution to add a setting for configuring the preferred language for auto-generated session history titles, as it directly addresses the user's need and provides a flexible solution for supporting multiple languages.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#inference speed#output truncation#response parsing#generation error#database connection

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING