{"version":"2.1.280","anchor":"git-worktree-telemetry-gains-private-layout-field","canonical_anchor":"git-worktree-telemetry-gains-private-layout-field","heading":"Git worktree telemetry gains private_layout field","tier":"internal","area":"Git Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/git-worktree-telemetry-gains-private-layout-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Git worktree telemetry gains private_layout field\n\nTelemetry for pinned git worktree layouts now records a private_layout field\n\n**Unclear.** The finding does not say what private_layout tracks or how it differs from work_tree_pinned.\n\n**What**\n\nWhen Claude Code records telemetry about a pinned git worktree layout (a setup where a project is checked out into a separate working directory pinned to it), the data it sends now includes a new `private_layout` true\/false field, alongside the existing `work_tree_pinned` and `names_read` fields.\n\n**Why**\n\nThis is an internal telemetry change with no visible effect on how Claude Code behaves day to day.\n\n- Area: Git Worktrees\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}