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

Claude Code v2.1.229 ·

Self-hosted runner can install launcher hooks sent by the server

The self-hosted runner writes server-supplied hook scripts for a session and deletes them afterwards.

You'll notice No documentation found New Features
JSON All of v2.1.229
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
New FeaturesKind: in v2.1.229,
New FeaturesSection of the release
What

When the server supplies hook scripts with a session, the runner validates and writes them under hooks/.ccr-launcher alongside a launcher-settings.json, then deletes them when the session ends. Scripts must have known event names, match ^[a-zA-Z0-9][a-zA-Z0-9_-]{0,62}\.(py|sh)$, and stay under a per-script size cap. A hooks path that is not a directory is refused.

Details
  • outcomes report through a new self_hosted_launcher_hooks telemetry family, including a distinct case where a repo settings file sets disableAllHooks:true
  • runner path only; nothing happens unless the server sends the hooks with the session
Evidence

self_hosted_launcher_hooks_validation_failed

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

Read from
Names in the bundlelauncher-settings.json

See this entry in the whole of v2.1.229 →

Feedback