{"version":"2.1.280","anchor":"new-telemetry-fields-for-gitfile-sync-sessions","canonical_anchor":"new-telemetry-fields-for-gitfile-sync-sessions","heading":"New telemetry fields for git\/file sync sessions","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-telemetry-fields-for-gitfile-sync-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New telemetry fields for git\/file sync sessions\n\nClaude Code's internal telemetry for git\/file sync sessions now includes three new fields\n\n**Unclear.** The finding does not say what data these fields actually capture or how they are used.\n\n**What**\n\nWhen Claude Code reports internal telemetry about sync sessions (the background process that keeps track of git and file state), the data it sends now includes three new optional fields: `servedLinked`, `firstUpload`, and `emptyUnreached`. These join the existing `endedEarlier` and `storageV5` fields already sent with this telemetry.\n\n**Why**\n\nThis is internal diagnostic data used to understand how sync sessions behave; it does not change any user-facing behavior or require any action from users.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}