Composer 2 Fast: Korean UTF-8 broken in chat and agent edits (Composer 2 OK)

Describe the Bug

Summary:
With the “Composer 2 Fast” model selected, Korean text is corrupted in the AI chat and in code/files modified by the Agent. With “Composer 2” (non-Fast) on the same machine, Korean displays correctly. Other editors and tools also show Korean correctly.

Environment:

  • OS: macOS (fill in version, e.g. 15.x)
  • Cursor: (fill in exact version from Cursor → About)
  • Problem model: Composer 2 Fast
  • Control: Composer 2 — Korean OK

Steps to reproduce:

  1. Set the chat/agent model to Composer 2 Fast.
  2. Ask for a reply in Korean, or use the Agent to edit a UTF-8 file that contains Korean.
  3. Observe mojibake / replacement characters in the chat and/or in saved file content.

Expected:
Korean should render and be written correctly as UTF-8, same as with Composer 2.

Actual:
Korean is corrupted only when Composer 2 Fast is selected.

Notes:
System locale and UTF-8 are not suspected; the issue is isolated to Composer 2 Fast in Cursor.

Steps to Reproduce

Steps to reproduce:

  1. Set the chat/agent model to Composer 2 Fast.
  2. Ask for a reply in Korean, or use the Agent to edit a UTF-8 file that contains Korean.
  3. Observe mojibake / replacement characters in the chat and/or in saved file content.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.0.16 (Universal)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
Layout: glass
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Same bug occurs on windows OS