Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.257 ·

New diagnostic when a daemon.lock names a PID this user can't signal

An unsignalable daemon lock PID is now checked for recycling or predating boot before the lock is replaced as stale.

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaSessionswhat it touches
KindInternal Changesin v2.1.257,
Under the hood

An unsignalable daemon lock PID is now checked for recycling or predating boot before the lock is replaced as stale.

When the supervisor can't signal a process referenced by daemon.lock for a reason other than ESRCH, it now checks via a new helper whether the PID is recycled or predates the current boot. If so, it writes a supervisor log line explaining that the lock is being replaced as stale, distinguishing predates_boot from a recycled PID belonging to another process.

Read from
Names in the bundledaemon.lock

See this entry in the whole of v2.1.257 →

Feedback