[BUG] Desktop Code tab: next-step box (wrap_up) recap and question come out in English in a non-English chat, buttons stay in the user's language
<img width="619" height="195" alt="Image" src="https://github.com/user-attachments/assets/9202cebe-17ac-414e-90d3-462cd65cb5e4" />
Environment
- Claude Desktop for Windows 2.37337.1.0, Code tab, local session
- Claude Code 2.1.295 (bundled), model claude-opus-5-5
- Windows 10
- Project
CLAUDE.mdtells the model to answer in the language of the user's message (Polish in this case)
What happens
The user writes in Polish, and the reply starts in Polish. When the model ends the turn with the wrap_up turn tool (recap, ask, actions), the next-step box mixes languages:
recap: Englishask: English- button labels (
actions[].label): Polish ("Zbuduj i sprawdź", "Sam zbuduję")
The reply text around the box also switches. It opens with a Polish paragraph, then continues in English ("The VS 2026 guide in Outline is up to date… The decision is in the box above. Run the build."). So one turn shows Polish and English side by side, and the box itself is half Polish, half English.
It happens repeatedly across sessions, not just once.
Steps to reproduce
- In a Code tab session, write to Claude in a language other than English (optionally with a
CLAUDE.mdrule to reply in that language). - Ask for something that ends with a decision for the user, for example: "Is the VS 2026 migration finished on my machine?", where the honest answer needs a build approval.
- Check the next-step box and the closing text.
Expected
The recap, ask, button labels and any closing text follow the conversation language, like the rest of the reply.
Likely cause
The wrap_up description, its field docs and its tool result are all in English, and recap/ask are full sentences. This looks like the same drift as #96326 (English tool output pulls the next reply into English). The short button labels usually stay in the user's language.
Possible fixes:
- State in the
wrap_updescription thatrecap,askand labels must use the conversation's language. - Or have the app pass the detected conversation language into the tool description/result.
Related
- #96326: replies drift into English after English tool output
- #99704: Opus 5.5 ignores the CLAUDE.md language rule (regression from Opus 5)
- #101940: same drift in the Windows desktop app; the
"language"setting and hooks don't fully help - #49336 (closed): "Recap language should follow chat language"
- #102132: another
wrap_upnext-step box issue (turn ends before the reply is written)