claude-code - 💡(How to fix) Fix Feature request: UI localization / i18n (Russian and other languages)

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…

Fix Action

Fix / Workaround

I've tried using the existing language setting in settings.json — it only affects Claude's text responses, not the UI strings. There is currently no workaround for UI localization; the strings are hardcoded in the extension binary.

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

Feature Request: UI Localization (i18n)

Claude Code's UI strings (permission dialogs, menus, buttons) are hardcoded in English. Please add localization support.

Requested language: Russian (ru-RU), and ideally a general i18n framework for other languages.

Affected UI elements:

  • Permission dialogs: "Allow this bash command?", "Yes", "No", "Never mind"
  • "Continue in Terminal", "Yes, allow ... for all projects"
  • All other hardcoded English strings

Motivation: The language setting already makes Claude respond in the user's language, but the UI stays in English — inconsistent experience for non-English speakers.

Suggested approach: Extract strings to locale files (locales/en.json, locales/ru.json) and respect the existing language setting in settings.json.

Proposed Solution

The interface should respect the existing language setting in ~/.claude/settings.json. When "language": "russian" is set, all UI strings (permission dialogs, menu items, buttons) should be displayed in Russian.

Alternatively, a dedicated uiLanguage setting could control the UI locale independently from the model's response language.

There should be locale files (e.g. locales/en.json, locales/ru.json) that the community can contribute translations to.

Alternative Solutions

I've tried using the existing language setting in settings.json — it only affects Claude's text responses, not the UI strings. There is currently no workaround for UI localization; the strings are hardcoded in the extension binary.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

No response

Additional Context

No response

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Feature request: UI localization / i18n (Russian and other languages)