Source Intelligence

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.225 Home All releases olderv2.1.224 v2.1.226newer

SDK spawn failures explain musl/glibc loader mismatches

Use it now
Useful3 Signal0
SDK not in their notes

SDK spawn errors now explain musl/glibc binary mismatches and tell you which option overrides the path.

options.pathToClaudeCodeExecutable
What

When the configured Claude Code executable exists but cannot be spawned, the SDK error now describes the dynamic-loader mismatch case and points at the option you would use to fix it.

Details
  • covers the case of a musl-linked binary on a glibc host, where /lib/ld-musl-* is absent
  • names options.pathToClaudeCodeExecutable as the override
Evidence

e.g. spawning a musl-linked binary on a glibc Linux host fails because the musl dynamic loader (/lib/ld-musl-*) is missing

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.225 →