-
v2.18.1 Stable
released this
2026-02-26 20:59:05 +03:00 | 92 commits to master since this release📅 Originally published on GitHub: Thu, 26 Feb 2026 17:59:21 GMT
🏷️ Git tag created: Thu, 26 Feb 2026 17:59:05 GMTWhat's Fixed
GitHub Copilot Garbled Characters — Root Cause Found (Issue #82)
v2.16.1 fixed the output pipe encoding but the issue persisted. The real root cause was on the read side, not the write side.
What was wrong:
All
Get-Contentcalls in the PS1 hook scripts had no-Encodingparameter. In PowerShell 5.x,Get-Contentwithout an explicit encoding reads files using the system ANSI code page (Windows-1252 in most Western locales). Any non-ASCII character intask_plan.mdorSKILL.md— emoji, CJK characters, accented letters — was corrupted before it ever reached the output pipe. Fixing the pipe encoding did nothing because the string was already garbled at the source.Secondary fix:
[System.Text.Encoding]::UTF8returns UTF-8 with BOM. Replaced with[System.Text.UTF8Encoding]::new($false)across all four PS1 scripts to prevent a stray0xEF 0xBB 0xBFpreamble from reaching JSON parsers.Fixed files:
pre-tool-use.ps1,session-start.ps1,agent-stop.ps1,post-tool-use.ps1Bash scripts were already correct from v2.16.1.
Contributors
- @Hexiaopi for confirming the issue persisted after v2.16.1 and keeping Issue #82 open
Full Changelog
https://github.com/OthmanAdi/planning-with-files/blob/master/CHANGELOG.md
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
mirror of
https://github.com/OthmanAdi/planning-with-files.git
synced 2026-04-25 16:06:02 +03:00