Composer suddenly switching to Chinese

[Joerg_Kunze (Jörg Kunze)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Incident Report

Incident: I suddenly responded in Chinese while the user was working on an English project in English.

Timeframe: During a session in which the user had been communicating in English and the workspace context (DigitalTwin/Doc, Basler product overview scripts) was entirely in English.

Parties And Environment

• User: jkunze
• Agent: Composer (Cursor AI)
• OS: Windows
• OS version: 10.0.22631
• Shell: PowerShell
• Workspace: c:\Users\jkunze\OneDrive - baslerweb.com\Research\DigitalTwin\Doc

What Happened (from transcript)

• User message (English): “There are a lots of lens, light and camera images contained in the svgs, that have a black background. Can you change them to transparent (preferred) or to white (if transparent is not possible?)”
• Agent response: In Chinese, asking about “继续” (continue) and 021/022 product docs, suggesting the user wanted to create or complete 021_排位报价产品需求.md and 022_xxx.md.
• The agent’s response was in the wrong language and addressed the wrong topic. The user had asked about SVG backgrounds, not about product docs or “继续.”
• The user had not created or referenced any non-English content. The conversation and workspace were entirely in English.

Steps to Reproduce

1. Open Cursor in an English-language workspace (DigitalTwin/Doc with Basler camera, lens, and light overview scripts).
2. Conduct the conversation entirely in English for many exchanges (cameras, lenses, lights, proxy, SVG changes, etc.).
3. Do not create or reference any non-English content.
4. Send a message in English about a technical task (e.g., changing black backgrounds in SVGs to transparent or white).
5. Observe the agent responding in Chinese and addressing a different topic (e.g., “继续” and 021/022 docs) instead of the user’s actual question.

Impact

• The user’s question (SVG backgrounds) was not answered.
• The response was in the wrong language and addressed the wrong topic.
• The user had to ask for clarification and correction.
• Consistency and predictability of the interaction were reduced.

Root Cause

• I mixed up context: I responded to a different topic (021/022 product docs, “继续”) instead of the user’s actual question (SVG black backgrounds → transparent/white).
• I switched to Chinese without any user request or non-English content in the conversation.
• I did not maintain the established language of the conversation.
• The user’s message was clear and in English; the error was internal context confusion, not ambiguity in the user’s input.

Corrective Actions

• I will maintain the language of the user’s messages and the project context.
• I will not switch to another language unless the user explicitly requests it.
• If the user’s message is ambiguous, I will default to the language of the current conversation and workspace.

Preventive Rule Going Forward

Match the user's language. Do not switch languages unless explicitly asked.

Current Status

Acknowledged. I will respond in English for this project unless you request otherwise.

Steps to Reproduce

please see bug description.

Expected Behavior

please see bug description.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.5.26 (user setup)
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.22631

For AI issues: which model did you use?

Composer 1.5

For AI issues: add Request ID with privacy disabled

04f812a5-a8f7-4204-929e-9a384b67a262

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the detailed report. Having the Request ID and a screenshot is really helpful.

This is a known issue with chat context where the agent gets confused and may switch to a different language or topic. We’ve seen similar reports from other users here: Extreme topic change upon return to agent conversation and here: !Reproducable! - Context pollution from a completely foreign project.

Your version (2.5.26, build from Feb 26) is older than the fix that shipped on March 9. Please update Cursor via Help > Check for Updates. That should help.

If it happens again after updating, please start a new chat (that’s the current workaround) and post back here. The team is aware, and your report helps us prioritize it.