Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.229 Home All releases ←olderv2.1.228 v2.1.231newer→
Claude Code v2.1.229

Windows guards for runner hooks that may not be reachable

Not switched on
Useful1 Signal2
Self-Hosted Runner not in their notes

The runner now has Windows errors for hooks and orchestrator mode, but they never fire.

Windows guards for --hooks-dir and orchestrator mode exist but the platform argument defaults to linux and no caller passes it.

--hooks-dirSELF_HOSTED_RUNNER_HOOKS_DIR
What

The self-hosted runner gained errors saying --hooks-dir, the matching SELF_HOSTED_RUNNER_HOOKS_DIR variable, and orchestrator mode are unsupported on Windows, because lifecycle hooks are POSIX executables spawned directly. Whether the guard can fire is unresolved in the code: the platform argument defaults to the literal "linux" and neither call site passes it.

Evidence

--hooks-dir is not supported on Windows: lifecycle hooks currently require a Linux or macOS host

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.229 →