Chris Z 93f9ed3d8f

fix(sandbox): force UTF-8 console for PowerShell so CJK output is not garbled (#5440) ...

* fix(sandbox): force UTF-8 console for PowerShell so CJK output is not garbled

LocalSandbox captures PowerShell output through a UTF-8 pipe reader
(errors=replace), but Windows PowerShell 5.1 writes console output in
the legacy OEM codepage (GBK on zh-CN Windows) unless told otherwise,
so every CJK character in tool output arrives as mojibake and the
decode never raises. Prepend a UTF-8 preamble
([Console]::InputEncoding/[Console]::OutputEncoding/$OutputEncoding)
to the -Command payload so both directions of the console are UTF-8
before the user command runs.

* fix(sandbox): pair PowerShell UTF-8 capture and guard console setup

---------

Co-authored-by: Willem Jiang <willem.jiang@gmail.com>

2026-09-15 07:31:03 +08:00

..

extension-api

feat(extensions): let an out-of-tree extension observe what the agent did (#4863)

2026-08-23 09:57:12 +08:00

harness

fix(sandbox): force UTF-8 console for PowerShell so CJK output is not garbled (#5440)

2026-09-15 07:31:03 +08:00