Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
WorktreesArea: what it touches
New FeaturesKind: in v2.1.248,
New FeaturesSection of the release
What
A background session whose recorded worktree path is the directory it starts in now adopts that worktree instead of ignoring it: it checks the git root, takes a worktree lock, retries once after 250 ms, and records the state. If any of that fails it logs a warning and carries on rather than aborting startup.
Details
Only runs when the session has a worktree path and the worktree was not created by a hook, plus several repository checks.
Evidence
[worktree] bg boot: adopted ${e} but no worktree lock names this process
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
