The cursor generated the plan.md file, but due to encoding issues, it displays unreadable characters

Support Bug Reports
7

Hey, thanks for the detailed report with the screenshot and the Request ID. There are two separate things here.

  1. Garbled text. This is a known bug. The agent Write and StrReplace tools save files as UTF-8 and don’t respect the project encoding, in your case GBK, so the new plan.md opens as �����. This has been reported and is being tracked, but I can’t share a specific ETA for a fix yet. There are already a lot of similar threads, for example It’s about the Chinese garbled text issue in the source code generated by the Cursor editor, can you take a look and fix it?.

  2. No encoding selector for .md. This is by design. .md files open in a custom rich-text Markdown editor that doesn’t have the standard encoding control in the status bar. To get the selector back, right click the file tab and choose Open With… then Text Editor, or use the Command Palette Ctrl+Shift+P then Change File Encoding.

As a workaround for now, your approach is fine. Explicitly ask the agent to generate the file in GBK. Let me know if any of this doesn’t work.