Bug in Cursor 3

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor 3 (user)
In editor mode, the model output is encoded in a messy way,

Copy and extract the file to C:\Users\miriers\AppData\Roaming\Cursor\User

Generally speaking, if the agent window is opened, cursor3 will output normal code. If there is messy code output, it must be because the user.settings.json file was not generated properly when switching to editor mode
Use the following replacement
{
“terminal.integrated.profiles.windows”: {

    "PowerShell": {
        "source": "PowerShell",
        "icon": "terminal-powershell"
    },
    "Command Prompt": {
        "path": [
            "${env:windir}\\Sysnative\\cmd.exe",
            "${env:windir}\\System32\\cmd.exe"
        ],
        "args": [],
        "icon": "terminal-cmd"
    },
    "Git Bash": {
        "source": "Git Bash"
    }
}

}
After actual testing, it was found that the editor mode of cusor3 displayed random characters from the beginning

If “terminal.integrated.profiles.windows” is accidentally generated at the beginning, although no error will be reported temporarily, it will revert to a messy code mode whenever the settings are changed. Therefore, it is not stable enough

After actual testing, the cursor2 version has been found to have normal coding
terminal.integrated.profiles

{
“terminal.integrated.profiles.windows”: {

    "PowerShell": {
        "source": "PowerShell",
        "icon": "terminal-powershell"
    },
    "Command Prompt": {
        "path": [
            "${env:windir}\\Sysnative\\cmd.exe",
            "${env:windir}\\System32\\cmd.exe"
        ],
        "args": [],
        "icon": "terminal-cmd"
    },
    "Git Bash": {
        "source": "Git Bash"
    }
}

}

Steps to Reproduce

cursor 2 is normal ,i downgrade the version

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Cursor 3 ide

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This is a known bug with encoding on Chinese Windows. When agent tools write files, they use the system ANSI code page (GBK) instead of UTF-8, so CJK characters turn into mojibake like in your screenshot.

The terminal.integrated.profiles.windows setting you mentioned isn’t the cause. It just happens to совпадение. The root issue is in the agent’s encoding pipeline.

Main thread with discussion and updates: Agent Write/StrReplace tools output GBK-encoded files on Chinese Windows — persists in 3.0.13 even after ACP changed to 65001 Please subscribe there to get updates.

We’re tracking this bug on our side, but we don’t have a firm ETA for a fix yet.