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.228 Home All releases olderv2.1.227 v2.1.229newer
Claude Code v2.1.228

Ancestor process checks no longer read a failed lookup as a no

Under the hood
Useful1 Signal1
Elsewhere

A failed process lookup is no longer mistaken for a confirmed no when checking parent processes.

What

Deciding whether a given process is an ancestor of this one now returns three states instead of true/false, so a lookup that produced no usable information is distinguished from one that positively ruled the process out.

Details
  • The result is only cached when the process start token read before and after walking the ancestor chain matches.
  • The shell command that walks the parent chain now emits explicit END and FAIL sentinels, so a truncated or failed walk is reported instead of being treated as an empty chain.
Evidence

no-evidence

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