Background-job startup now reclaims worktrees first, with timing recorded.
What's wrong with this entry?
When starting in background-job mode, Claude Code now reads job state and runs a worktree reclaim before background jobs begin, timed by a new setup_bg_worktree_adopt_ms metric.
- Only reached on the background-job startup path; ordinary interactive startup is unaffected.
- A failure logs "[worktree] bg adopt-time reclaim skipped" and startup continues.
[worktree] bg adopt-time reclaim skipped
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.
-
v2.1.223
Background job state and roster writes can route through the v5 storage backend
Both mention background
-
v2.1.223
Telemetry for transient background-job state read failures
Both mention background
-
v2.1.223
Roster orphan adoption reports itself
Both mention background