release: bump to 1.0.3 with chcp 65001 + WSL UTF-8 locale before agent exec

Fixes Chinese-input garbling when typing into hermes / openclaw gateway
from the PowerShell window the Windows installer hands off to.

Background: setting [Console]::OutputEncoding / InputEncoding to UTF-8
(done in wsl-common.ps1 previously) only affects the CURRENT PowerShell
process.  Child processes — cmd.exe, wsl.exe, and anything spawned from
bash inside the distro — inherit the console's CODEPAGE, not .NET's
Encoding property.  On zh-CN hosts that codepage is still 936 (GBK), so
keystrokes reach hermes as GBK bytes and the agent garbles them on the
UTF-8 decode.

Add Set-ConsoleUtf8CodePage (runs `chcp 65001` via cmd.exe) to
wsl-common.ps1 and call it right before each `wsl.exe -- bash -lc ...`
handoff in install-hermes.ps1 / install-openclaw.ps1.  Also prepend
LANG=C.UTF-8 LC_ALL=C.UTF-8 to the bash command so readline-based tools
inside WSL read multibyte input correctly regardless of the distro's
default locale.

We don't call chcp at installer start because our own Write-Host output
is already UTF-8-correct via the .NET Encoding setters; flipping the
codepage that early would risk minor rendering inconsistencies during
the long-running install.

Version strings bumped in installer.iss, build-pkg.sh, and README tables.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: yysjasmine

README.md

@@ -89,9 +89,9 @@ Pre-built installers live on the [GitHub Releases page](https://github.com/Sense
 
 | Platform | Download | How to Use |
 |----------|----------|------------|
-| Windows | [`AgentPack-1.0.2-windows-x64.exe`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-windows-x64.exe) | Double-click and follow the wizard; installation runs inside WSL2, and the PowerShell window is taken over by the installed agent when setup finishes |
-| macOS | [`AgentPack-1.0.2-macos-universal.pkg`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-macos-universal.pkg) | Double-click, then complete setup in the Terminal window that opens; the same window becomes the agent's REPL / gateway once installation finishes |
-| Linux | [`AgentPack-1.0.2-linux.sh`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-linux.sh) *or* the one-liner below | Download and run `chmod +x AgentPack-1.0.2-linux.sh && ./AgentPack-1.0.2-linux.sh`, or paste `curl -fsSL https://raw.githubusercontent.com/SenseTime-FVG/agent_pack/main/linux/install.sh \| bash` — either way the shell that ran the installer is handed over to the agent via `exec` |
+| Windows | [`AgentPack-1.0.3-windows-x64.exe`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.3-windows-x64.exe) | Double-click and follow the wizard; installation runs inside WSL2, and the PowerShell window is taken over by the installed agent when setup finishes |
+| macOS | [`AgentPack-1.0.3-macos-universal.pkg`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.3-macos-universal.pkg) | Double-click, then complete setup in the Terminal window that opens; the same window becomes the agent's REPL / gateway once installation finishes |
+| Linux | [`AgentPack-1.0.3-linux.sh`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.3-linux.sh) *or* the one-liner below | Download and run `chmod +x AgentPack-1.0.3-linux.sh && ./AgentPack-1.0.3-linux.sh`, or paste `curl -fsSL https://raw.githubusercontent.com/SenseTime-FVG/agent_pack/main/linux/install.sh \| bash` — either way the shell that ran the installer is handed over to the agent via `exec` |
 
 ## Building from Source
 
@@ -104,7 +104,7 @@ cd windows
 iscc installer.iss
 ```
 
-Output: `dist/AgentPack-1.0.2-windows-x64.exe`
+Output: `dist/AgentPack-1.0.3-windows-x64.exe`
 
 ### macOS (.pkg)
 
@@ -115,7 +115,7 @@ cd macos
 ./build-pkg.sh
 ```
 
-Output: `dist/AgentPack-1.0.2-macos-universal.pkg`
+Output: `dist/AgentPack-1.0.3-macos-universal.pkg`
 
 ### Linux
 

README.zh-CN.md

@@ -88,9 +88,9 @@ Bundled skills 已经直接放进 `repos/hermes-agent/skills/` 和 `repos/opencl
 
 | 平台 | 下载 | 使用方式 |
 |------|------|---------|
-| Windows | [`AgentPack-1.0.2-windows-x64.exe`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-windows-x64.exe) | 双击运行向导；安装过程在 WSL2 中执行，安装完成后当前 PowerShell 窗口会被接管，直接跑起 agent |
-| macOS | [`AgentPack-1.0.2-macos-universal.pkg`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-macos-universal.pkg) | 双击后在自动打开的 Terminal 窗口中完成安装；安装结束后同一个窗口会变成 agent 的 REPL / gateway |
-| Linux | [`AgentPack-1.0.2-linux.sh`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-linux.sh) 或下面的一行命令 | 下载后 `chmod +x AgentPack-1.0.2-linux.sh && ./AgentPack-1.0.2-linux.sh`，或直接粘贴 `curl -fsSL https://raw.githubusercontent.com/SenseTime-FVG/agent_pack/main/linux/install.sh \| bash` — 两种方式都会在安装结束后用 `exec` 在当前 shell 里拉起 agent |
+| Windows | [`AgentPack-1.0.3-windows-x64.exe`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.3-windows-x64.exe) | 双击运行向导；安装过程在 WSL2 中执行，安装完成后当前 PowerShell 窗口会被接管，直接跑起 agent |
+| macOS | [`AgentPack-1.0.3-macos-universal.pkg`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.3-macos-universal.pkg) | 双击后在自动打开的 Terminal 窗口中完成安装；安装结束后同一个窗口会变成 agent 的 REPL / gateway |
+| Linux | [`AgentPack-1.0.3-linux.sh`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.3-linux.sh) 或下面的一行命令 | 下载后 `chmod +x AgentPack-1.0.3-linux.sh && ./AgentPack-1.0.3-linux.sh`，或直接粘贴 `curl -fsSL https://raw.githubusercontent.com/SenseTime-FVG/agent_pack/main/linux/install.sh \| bash` — 两种方式都会在安装结束后用 `exec` 在当前 shell 里拉起 agent |
 
 ## 从源码构建
 
@@ -103,7 +103,7 @@ cd windows
 iscc installer.iss
 ```
 
-产物：`dist/AgentPack-1.0.2-windows-x64.exe`
+产物：`dist/AgentPack-1.0.3-windows-x64.exe`
 
 ### macOS (.pkg)
 
@@ -114,7 +114,7 @@ cd macos
 ./build-pkg.sh
 ```
 
-产物：`dist/AgentPack-1.0.2-macos-universal.pkg`
+产物：`dist/AgentPack-1.0.3-macos-universal.pkg`
 
 ### Linux
 

macos/build-pkg.sh

@@ -8,7 +8,7 @@ SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
 BUILD_DIR="$SCRIPT_DIR/build"
 DIST_DIR="$PROJECT_ROOT/dist"
-VERSION="1.0.2"
+VERSION="1.0.3"
 SCRIPTS_DIR="$BUILD_DIR/scripts"
 
 rm -rf "$BUILD_DIR"

windows/installer.iss

@@ -2,7 +2,7 @@
 ; Requires Inno Setup 6.x
 
 #define MyAppName "Agent Pack"
-#define MyAppVersion "1.0.2"
+#define MyAppVersion "1.0.3"
 #define MyAppPublisher "Agent Pack"
 #define MyAppURL "https://github.com/SenseTime-FVG/agent_pack"
 

windows/scripts/install-hermes.ps1

@@ -93,4 +93,13 @@ Set-Content -LiteralPath (Join-Path $markerDir "hermes-installed.marker") `
 Write-Host ""
 Write-Host "[OK] Hermes Agent installed. Starting hermes in this window..." -ForegroundColor Green
 Write-Host ""
-& wsl.exe -- bash -lc 'hermes'
+
+# Switch the console codepage to UTF-8 before handing off, so Chinese
+# characters typed into the hermes REPL reach the agent as UTF-8 bytes
+# (not GBK) on zh-CN Windows hosts.
+Set-ConsoleUtf8CodePage
+
+# Force a UTF-8 locale inside WSL for the hermes process.  Some readline-
+# based REPLs misread multibyte input when LANG is unset or C, even with
+# the console codepage already set to 65001 on the Windows side.
+& wsl.exe -- bash -lc 'LANG=C.UTF-8 LC_ALL=C.UTF-8 hermes'

windows/scripts/install-openclaw.ps1

@@ -118,4 +118,12 @@ Write-Host ""
 Write-Host "[OK] OpenClaw installed. Starting gateway in this window..." -ForegroundColor Green
 Write-Host "[*] Opening OpenClaw dashboard in your browser shortly..." -ForegroundColor Cyan
 Write-Host ""
-& wsl.exe -- bash -lc 'openclaw gateway --verbose'
+
+# Switch the console codepage to UTF-8 before handing off, so log output
+# from openclaw (which emits UTF-8) renders correctly and any Chinese
+# typed in future `openclaw` subcommands reaches the gateway as UTF-8.
+Set-ConsoleUtf8CodePage
+
+# Force a UTF-8 locale inside WSL so openclaw's log formatter and any
+# multibyte input forwarded into the gateway read as UTF-8.
+& wsl.exe -- bash -lc 'LANG=C.UTF-8 LC_ALL=C.UTF-8 openclaw gateway --verbose'

windows/scripts/wsl-common.ps1

@@ -14,6 +14,26 @@ try {
     # ignore the failure rather than aborting the install.
 }
 
+# Flip the whole console's codepage to UTF-8 (65001).  Unlike the
+# [Console]::OutputEncoding setter above — which only affects text THIS
+# PowerShell process reads/writes — `chcp 65001` changes the codepage for
+# the console AS A WHOLE, which is what child processes (cmd.exe, wsl.exe,
+# and anything spawned from them) inherit.  Without this, typing Chinese
+# into a `hermes` REPL that we exec via `wsl.exe -- bash -lc 'hermes'`
+# sends GBK bytes, which the agent decodes as UTF-8 and garbles.
+# Call this right before exec'ing the agent so our own Write-Host output
+# (already UTF-8) isn't affected while the installer is still speaking.
+function Set-ConsoleUtf8CodePage {
+    # `chcp` is a cmd.exe builtin — shell out to cmd to avoid PowerShell
+    # complaining that the command isn't a file.  Swallow output: chcp
+    # prints "Active code page: 65001" which is just noise for the user.
+    try {
+        & cmd.exe /c 'chcp 65001 >NUL 2>&1'
+    } catch {
+        # Ignore — at worst the user retains the system default codepage.
+    }
+}
+
 $script:RegionChecked = $false
 $script:IsChinaRegion = $false