claude-code - 💡(How to fix) Fix Language instruction ignored: Claude responds in Japanese despite explicit Traditional Chinese requirement in CLAUDE.md [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#46846Fetched 2026-04-12 13:31:31
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

Claude Code repeatedly responds in Japanese or Korean despite an explicit instruction in CLAUDE.md to always use Traditional Chinese (台灣正體中文) and never use Japanese, Korean, or Simplified Chinese.

Root Cause

Claude Code repeatedly responds in Japanese or Korean despite an explicit instruction in CLAUDE.md to always use Traditional Chinese (台灣正體中文) and never use Japanese, Korean, or Simplified Chinese.

Code Example

## 語言設定

永遠使用台灣正體中文回覆,不得使用日文、韓文或簡體中文。
RAW_BUFFERClick to expand / collapse

Summary

Claude Code repeatedly responds in Japanese or Korean despite an explicit instruction in CLAUDE.md to always use Traditional Chinese (台灣正體中文) and never use Japanese, Korean, or Simplified Chinese.

Environment

  • Claude Code version: unknown (VSCode extension)
  • Model: claude-sonnet-4-6
  • Platform: macOS (darwin 24.6.0)

CLAUDE.md instruction

## 語言設定

永遠使用台灣正體中文回覆,不得使用日文、韓文或簡體中文。

What happened

This has occurred across multiple sessions. Claude switches to Japanese or Korean mid-conversation during technical work, despite the CLAUDE.md instruction being loaded and visible in context.

Example 1 (screenshot provided)

After a git push operation, Claude responded entirely in Japanese — then caught itself, apologized in Japanese, and continued to respond in Japanese while attempting to correct the issue:

commit と push 完了。lint-staged の index.lock エラーは先ほどの background プロセスの残骸で、最終的には成功している。

申し訳ありません、日本語になっていました。再度、正體中文で: storefront に push 完了しました。...

The "correction" was itself still in Japanese.

Example 2 (this session)

After a gh pr view tool call returning English-only JSON, Claude responded in Japanese:

Backend tests が FAILURE のままです。CI が通っていない状態では merge できません。

ただ、このPR(chore/codex-pr-review-agents)の内容は AGENTS.md への変更で...

Example 3 (reported, no screenshot)

The user has also received Korean responses on separate occasions.

What should have happened

All responses should be in Traditional Chinese regardless of the operation being performed.

Key observations

  • The project codebase contains only Traditional Chinese and English — no Japanese or Korean anywhere in the repo
  • All team members write in Traditional Chinese; other team members do NOT experience this issue with their own Claude Code sessions
  • The violation occurs after tool calls (git, gh) that return English-only output — there is no Japanese or Korean content in the conversation context that could explain the language switch
  • After being corrected, Claude sometimes apologizes and "switches back" — but the apology itself is still in Japanese
  • The issue recurs across sessions despite being recorded in both CLAUDE.md and the auto-memory system
  • The pattern is specific to this one user, suggesting something in their session context or environment triggers it — but what that is remains unknown

extent analysis

TL;DR

The issue can be mitigated by ensuring the CLAUDE.md instruction is correctly loaded and parsed by Claude Code, potentially by verifying the file encoding and formatting.

Guidance

  • Verify that the CLAUDE.md file is encoded in UTF-8 and has the correct formatting to ensure it is properly loaded by Claude Code.
  • Check the Claude Code version and model configuration to see if there are any known issues or updates that may address the language switching problem.
  • Investigate the session context and environment to identify any factors that may be triggering the language switch, such as specific tool calls or output.
  • Consider testing with a minimal CLAUDE.md file containing only the language instruction to isolate the issue.

Example

No code snippet is provided as the issue is related to the interaction between Claude Code and the CLAUDE.md file, and no specific code changes are implied.

Notes

The issue seems to be specific to this one user and may be related to their session context or environment. Further investigation is needed to determine the root cause of the problem.

Recommendation

Apply workaround: Verify and adjust the CLAUDE.md file and session context to ensure correct loading and parsing of the language instruction, as the root cause of the issue is still unknown.

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