Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.229 ·

Windows guards for runner hooks that may not be reachable

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

Nothing to try yet No documentation found In Development
JSON All of v2.1.229
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
In DevelopmentKind: in v2.1.229,
In DevelopmentSection of the release

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

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.

Read from

See this entry in the whole of v2.1.229 →

Feedback