Claude Code v2.1.221 ·
Process markers gain a second, currently-unused start-time field
Process marker files can write an alternate start-time field, but that path is hard-coded off.
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Background TasksArea: what it touches
In DevelopmentKind: in v2.1.221,
In DevelopmentSection of the release
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.
See this entry in the whole of v2.1.221 →
