On Windows, Chinese prompt in hooks stdin becomes "?" while execution.log shows correct text

[Colin]

Hey!

Thanks for the report.

I believe that this was reported here already:

Windows: Cursor Hooks corrupt Chinese (UTF-8) characters in stdin - replaced with question marks

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug When Cursor invokes hook scripts on Windows, Chinese (and potentially all non-ASCII UTF-8) characters in the JSON data passed via stdin are corrupted and replaced with question marks (? / 0x3F). Key Finding: The corruption happens before the data reaches the Python script. Analysis of the raw binary data confirms that Chinese characters are already replaced with 0x3f (question mark ASCII) in the stdin stream. Steps to Re…

And I’ve linked this thread to the internal ticket.