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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Process markers gain a second, currently-unused start-time field

Under the hood
Useful1 Signal1
Background Tasks

Process marker files can write an alternate start-time field, but that path is hard-coded off.

A second process start-time field exists in the writer, disabled by a constant predicate.

What

Process marker writing was routed through a helper that can emit an alternate start-time field, but the switch is off in this build.

Details
  • covers both the daemon/PID marker and the fleet gesture record
  • the helper emits either procStart or the new procStartFt, chosen by a predicate hard-coded to return false here
  • the on-disk shape is therefore unchanged; the reader already understands both fields
Evidence

procStartFt

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