OpenCode plugin that fixes UTF-8 encoding issues when executing shell commands on Windows. Zero npm runtime dependencies.
When OpenCode runs shell commands on Windows, the console output encoding defaults to the system locale (e.g., GBK for zh-CN). This causes garbled text when LLM-generated commands produce UTF-8 output — breaking file paths, error messages, and all non-ASCII content.
This plugin hooks into OpenCode's tool.execute.before event, detects the configured shell from OpenCode's config (config.shell), and injects the matching UTF-8 encoding configuration before every shell command:
PowerShell (pwsh):
[Console]::OutputEncoding=[Console]::InputEncoding=[Text.Encoding]::UTF8;$OutputEncoding=[Text.Encoding]::UTF8;$env:PYTHONIOENCODING='utf-8';Bash / POSIX shells (bash, zsh, sh, ...):
export LC_ALL=C.UTF-8; export LANG=C.UTF-8; export PYTHONIOENCODING=utf-8;Command Prompt (cmd):
chcp 65001 >nul- Shell auto-detection — reads
config.shellfrom OpenCode at startup; falls back to platform detection (pwshon Windows,bashelsewhere) when unset or unavailable - Automatic injection — applies to all
bashandshelltool calls - Idempotent — skips commands that already contain the shell's encoding marker (
OutputEncoding/LC_ALL/chcp) to avoid duplication setprefix aware — preserves PowerShellset VAR="value"prefixes before injecting- Zero config — works out of the box with no options
- Debug logging off by default — set
OPENCODE_UTF8_DEBUG=1to enable diagnostic logging to$TMP/utf8-plugin.log
npm install opencode-windows-encodingAdd the plugin to your opencode.jsonc:
Or with a specific version:
{
"plugin": [
"opencode-windows-encoding@^1.1"
]
}After adding the plugin, restart OpenCode. All subsequent shell commands will use UTF-8 encoding automatically.
Since v4.1.0 the main line works on both V1 and V2 hosts — no separate dist-tag is needed:
{
"plugin": [
"opencode-windows-encoding@latest"
]
}The default export is a combined { id, server, setup } module:
- V1 hosts (opencode ≤ 1.17, or a local path reference on 1.18.x) call
serverand inject viatool.execute.before. - V2 hosts validate
id+setup. The setup registers theshell create.beforehook on hosts that expose a shell hook domain (contract verified against the opencode dev branch; the resolved shell is provided directly onevent.shell, so noconfig.shelllookup is needed). On V2 hosts without the shell domain (e.g. opencode 1.18.x) the setup degrades to a no-op — the plugin loads cleanly and activates automatically once the host gains the hook.
Note: the legacy
betadist-tag (opencode-windows-encoding@beta) is deprecated — the main line supersedes it.
The built V1 plugin is a single self-contained JavaScript file (the shared core is bundled inline). From a clone of this repo:
npm install && npm run buildThen copy dist/v1.js to OpenCode's plugins directory with a .ts extension (opencode 1.18.x auto-discovery resolves .js files unreliably on Windows; the bundled output is plain ESM JavaScript, which loads fine as .ts):
PowerShell:
Copy-Item dist/v1.js $env:USERPROFILE/.config/opencode/plugins/utf8-encoding.tsBash / WSL:
cp dist/v1.js ~/.config/opencode/plugins/utf8-encoding.tsRestart OpenCode to apply.
The built file uses only Node.js built-ins (node:fs, node:os, node:path) and a compile-time-only import type from @opencode-ai/plugin — zero npm runtime dependencies.
- OpenCode (any recent version with plugin support)
- Windows (this plugin is designed specifically for Windows encoding issues)
- Any of: PowerShell 7+ (
pwsh), Bash, or Command Prompt (cmd)
# Install dependencies
npm install
# Build
npm run build
# Type check
npm run typecheck
# Watch mode (for development)
npm run devReference the source file directly:
{
"plugin": [
"/path/to/opencode-windows-encoding/src/v1.ts"
]
}AGPL-3.0 — see LICENSE for details.
{ "plugin": [ "opencode-windows-encoding" ] }