win-hooks 1.13.0

The run you could not see, and the one that never happened

win-hooks now says one line at the start of every session: which host it checked, how many hook files it looked at, how many it repaired, and what is still open. Until now a quiet session meant either a clean machine or a hook that never fired, and nothing you could read told you which one you had.

On Codex it was usually the second. Every hook win-hooks patched was failing at exit 1 with no output, because the Windows command it wrote was assumed to reach cmd.exe and was handed to PowerShell instead, which reads a leading quoted path as an expression and rejects the argument after it. Patched hooks now open with cmd /c, the one form Windows PowerShell 5.1, pwsh 7, and cmd.exe all execute, and the test materializes the real command and runs it through every edition installed on the machine.

One thing to know when you upgrade on Codex: Codex remembers a hash of each hook it trusts, and this release changes the hook manifest, so it stops dispatching win-hooks' own hooks until you trust them again. It does that silently, with no warning and no error. npx @lilmgenius/win-hooks patch still repairs everything from outside the hook, and win-hooks will never write that trust record on your behalf.

New

• A line at session start naming the host, the hook files checked, the repairs made, and the issues left open. Only at session start: nothing else writes where a model would read it on every prompt.

Fixed

• Every patched Codex hook ran and failed, leaving no output and no heartbeat. The Windows command now opens with cmd /c, and a hook patched before this release is re-derived on the next run. A commandWindows a plugin author wrote is still left alone.

Also

• The suite executes the real emitted command from a plugin folder whose name contains a space, under every PowerShell edition present, rather than stopping at the first shell that works. Coverage: 30 of 30 testable cases, one waived in writing.
• Nothing win-hooks ships can write Codex's hook-trust record, and a test holds it to that. A repair tool able to grant itself hook trust would be a supply-chain hole.

Everything win-hooks repairs is listed in the README.

Install

# Claude Code
claude plugin marketplace add LilMGenius/win-hooks && claude plugin install win-hooks

# Codex
codex plugin marketplace add LilMGenius/win-hooks && codex plugin add win-hooks@win-hooks

# or a one-shot CLI fix
npx @lilmgenius/win-hooks