ponytail/hooks
Ben Younes 147bcfd621
fix: use PowerShell $env: syntax for Windows hook paths (#26)
On Windows the lifecycle hooks run via PowerShell, which does not expand
cmd.exe-style %CLAUDE_PLUGIN_ROOT%. The path was passed literally, so the hook
launcher could not find the script and both SessionStart and UserPromptSubmit
failed with exit code 1 (issue #19). Switch the two commandWindows entries to
$env:CLAUDE_PLUGIN_ROOT, keeping the working node + .js invocation.

Add a regression test that rejects cmd.exe %VAR% syntax in commandWindows and
asserts every hook command points at a script that actually ships in hooks/.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-14 17:39:59 +02:00
..
hooks.json fix: use PowerShell $env: syntax for Windows hook paths (#26) 2026-06-14 17:39:59 +02:00
ponytail-activate.js feat: add pi extension (#1) 2026-06-12 17:55:24 +02:00
ponytail-config.js feat: add pi extension (#1) 2026-06-12 17:55:24 +02:00
ponytail-instructions.js fix: stop mode filter stripping rule bullets with a colon 2026-06-13 01:43:26 +02:00
ponytail-mode-tracker.js feat: codex support 2026-06-12 08:49:33 -04:00
ponytail-runtime.js feat: codex support 2026-06-12 08:49:33 -04:00
ponytail-statusline.ps1 feat: full plugin integration + cross-agent rules 2026-06-12 03:25:15 +02:00
ponytail-statusline.sh feat: full plugin integration + cross-agent rules 2026-06-12 03:25:15 +02:00