{"version":"2.1.295","anchor":"first-party-event-logging-gains-tenant-send-rules-and-git","canonical_anchor":"first-party-event-logging-gains-tenant-send-rules-and-git","heading":"Usage data now records whether your git working copy was clean at start","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/first-party-event-logging-gains-tenant-send-rules-and-git","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Usage data now records whether your git working copy was clean at start\n\nUsage data now notes whether your git working copy had changes when the session started, and some usage data can be held back from sending\n\n**What**\n\nUsage data is the information Claude Code sends to Anthropic about how it is used. Each event now carries three facts about your git project as it was when the session started:\n\n- whether there were no uncommitted changes\n\n- how many files were changed\n\n- how many files git was not tracking\n\nIn a new mode, Claude Code may also refuse to send usage data, for example when it has no credential or is doing a dry run, and it counts what was sent and what was dropped. In that mode it marks requests as test traffic outside production, does not follow redirects, and can accept a `CLAUDE_CODE_OAUTH_TOKEN` that starts with `sk-ant-oat`. Error reporting also has an extra check that can stop it early.\n\n**Why**\n\nThe usage data now includes counts of changed and untracked files in your project at the start of each session.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}