[Bug] PowerShell parser fails on non-ASCII characters in first tool call due to codepage 932 encoding
Status Open
Reported on v2.1.233
Maintainer reply None cached
Activity 0 comments · opened Aug 15, 2026
Bug Description
Windows + Japanese path + codepage 932.
The first PowerShell tool call of each session fails with
"Invalid JSON from PowerShell parser" when the command contains
non-ASCII characters. Re-running the identical command succeeds.
The syntax-check process appears to start in CP932 before the
UTF-8 setup applies.
Environment Info
- Platform: win32
- Terminal: null
- Version: 2.1.233
- Feedback ID: 4106f4cb-868c-4f67-a1d1-d7901282d3c0
Errors
[]