Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Git WorktreesArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
Unclear The finding does not say what the warning looks like to the user or exactly when the empty check is triggered.
What
Claude Code syncs session data across git worktrees (separate working copies of the same repository checked out at once). When a session's sync record is created but ends up with no writes to it, Claude Code now writes a small marker file recording that the session is empty.
When something later attaches to that session directory, it can check this marker and be warned that the session is empty, rather than treating it as a normal session with no indication anything is off.
Why
This prevents confusion when reopening a session tied to a git worktree that never actually received any data: instead of looking like a normal, silently empty session, it can now be flagged as such.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what the warning looks like to the user or exactly when the empty check is triggered.
