Source Intelligence
Follow Discord

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→
Claude Code v2.1.225

PID 1 no longer counts as an ancestor when verifying a peer connection

You'll notice
Useful2 Signal0
Cross-Session Messaging

Sessions running as the main process in a container no longer get wrongly matched to peer connections.

What

Ancestor verification for peer connections no longer treats a container init process as a legitimate ancestor, so a session running under PID 1 cannot be matched by accident.

Details
  • the Linux /proc ancestor walk now records a parent pid of 1 and stops there, where it previously discarded it by breaking at ppid <= 1
  • the array descendant helper returns false immediately for pid 1 (if (t === 1) return !1)
  • the cached lookup now requires process.pid !== 1 && i.includes(process.pid)
  • gated by platform: the ancestor walk reads /proc, so this is the Linux path
Evidence

[peer-cred] peer pid lookup failed

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.225 →