{"version":"2.1.265","anchor":"git-working-tree-snapshot-sync-now-records-detailed-timing-s","canonical_anchor":"git-working-tree-snapshot-sync-now-records-detailed-timing-s","heading":"Git working-tree snapshot sync now records detailed timing stats","tier":"internal","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/git-working-tree-snapshot-sync-now-records-detailed-timing-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Git working-tree snapshot sync now records detailed timing stats\n\nGit status syncing now records how long the file listing and history read each took\n\n**What**\n\nWhen Claude Code takes a snapshot of your git working tree's state (used to keep track of file and commit changes), it now records timing details: `listingMs` (time spent listing the working tree), `historyMs` (time spent reading commit history), and `listingEmpty` (whether the listing came back empty).\n\n**Why**\n\nThis is internal diagnostic data that helps identify whether slowness in git syncing comes from listing files or reading history, rather than a change you'll notice directly.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}