{"version":"2.1.280","anchor":"git-worktree-session-sync-writes-an-empty-session-marker","canonical_anchor":"git-worktree-session-sync-writes-an-empty-session-marker","heading":"Git-worktree session sync writes an 'empty session' marker","tier":"internal","area":"Git Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/git-worktree-session-sync-writes-an-empty-session-marker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Git-worktree session sync writes an 'empty session' marker\n\nClaude Code now marks a synced git-worktree session as empty when it was created but never received any writes\n\n**Unclear.** The finding does not say what the warning looks like to the user or exactly when the empty check is triggered.\n\n**What**\n\nClaude 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.\n\nWhen 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.\n\n**Why**\n\nThis 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.\n\n- Area: Git Worktrees\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}