Mixed or corrupted context in chinese

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

get an answer in a wrong language (chinese) and not related to the project.

Steps to Reproduce

I tested multiple times with composer 1.5 and composer 2. Seems the word that cause the issue is “implement”.

Expected Behavior

it has to only create a plan, not to modify all my project with a foreigner project in other language.

Screenshots / Screen Recordings

composer15.andcomposer2chinese.jpg
composer15.andcomposer2chinese.jpg1018×2250 324 KB

Operating System

Windows 10/11

Version Information

Version: 2.6.22 (user setup)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

composer 1.5 and composer 2

For AI issues: add Request ID with privacy disabled

cee9495c-56f2-4240-af12-466cad0f3b50

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report and the request ID, we confirmed this on our end.

This is a known issue with the Composer models where they hallucinate CJK text and unrelated project content. Important note: this is not a data leak from another user. The model generates fictional content like project names, file paths, and commands that looks real but is not from anyone’s actual codebase. It’s hallucinated training data, not cross-session contamination.

We’ve seen the same pattern from several users recently:

The team is aware and tracking this. Your request ID helps us gauge the scope.

Workarounds for now:

  • Start a new chat if it happens
  • Switch to a non-Composer model like Claude or GPT to avoid it entirely

Let me know if you keep running into this.

8

Hey @lordz!

The mixed/corrupted context language issue has been addressed in a recent Cursor update. Updating to the latest version should resolve this.