You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: use forward slashes in hook paths for bash compatibility
On Windows, Claude Code and Gemini CLI execute hook commands via bash
(Git Bash / MSYS2). GetModuleFileNameW returns backslash paths like
D:\app\toasty\toasty.exe, but unquoted backslashes in bash are escape
characters — \a becomes a (bell), \t becomes tab — mangling the path
to D:apptoastytoasty.exe ("command not found").
Additionally, escape_json_string() manually escapes backslashes for
JSON, but WinRT's JsonValue::CreateStringValue + Stringify already
handles JSON serialization, causing double-escaping.
Fix: normalize exe path to forward slashes (D:/app/toasty/toasty.exe)
before building the hook command. Forward slashes are accepted by
Windows APIs and safe in all shell contexts.
Affects: install_claude(), install_gemini(), and their dry-run output.
0 commit comments