Claude Code v2.1.225 · 7 Aug 2026
SDK spawn failures explain musl/glibc loader mismatches
SDK spawn errors now explain musl/glibc binary mismatches and tell you which option overrides the path.
Use it now Tier: how much it should matter to you
3 Useful: my rating, 1 to 5
0 Signal: worth watching, 1 to 5
SDK Area: what it touches
Improvements Kind: in v2.1.225, 07 Aug 26
What probably matters to you Section of the release
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.
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 →
7 Aug 2026 · 155 entries, this one is #25.
Use it now15 You'll notice87 Nothing to try yet16 Under the hood37
Open the release →
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 24 of 155
SDK can defer permission mode resolution to the CLI
Use it now SDK
In v2.1.225 What probably matters to you release-page order
Next → · 26 of 155
CLAUDE_REMOTE_TOOLS_BRIDGE_URL added to the remote-settings env filter
You'll notice Settings