Source Intelligence
Reading a new release v2.1.251 Analysing changes · 2/5 Sorting the findings · 1/4 steps 470 findings $18.91 so far

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.49 Home All releases olderv2.1.48 v2.1.50newer
Claude Code v2.1.49

HTTP Hooks Temporarily Disabled

What

HTTP hooks defined in your configuration will no longer execute. Instead, they return immediately with a "HTTP hooks are not yet supported" message.

Impact:

  • If you have configured HTTP hooks (using type: "http" in your hooks configuration), they will not execute in this version
  • The hook will be skipped rather than failing the operation—your workflow will continue without the HTTP call
  • Bash hooks (type: "bash") continue to work normally

Example log output when an HTTP hook is encountered:

Hooks: skipping HTTP hook https://example.com/hook — HTTP hooks are not yet supported

Workaround: If you rely on HTTP hooks, you can convert them to bash hooks that use curl to make the HTTP request:

{
  "type": "bash",
  "command": "curl -X POST -H 'Content-Type: application/json' -d '$HOOK_PAYLOAD' https://example.com/hook"
}
Evidence

Hook execution skips HTTP hooks with message (search for "HTTP hooks are not yet supported")

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

See this entry in the whole of v2.1.49 →