{"version":"2.1.284","anchor":"new-git-state-fields-in-the-telemetry-event-proto-have-no-pr","canonical_anchor":"new-git-state-fields-in-the-telemetry-event-proto-have-no-pr","heading":"Telemetry event format gains git remote and working-tree fields, not yet filled","tier":"soon","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/new-git-state-fields-in-the-telemetry-event-proto-have-no-pr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Telemetry event format gains git remote and working-tree fields, not yet filled\n\nThe telemetry event format adds fields for the git remote URL and working-tree state at session start, but nothing fills them yet\n\n**What**\n\nTelemetry is the usage data Claude Code sends back. The format it uses for events has four new fields about your git repository:\n\n- `git_remote_url`: the address of the repository's remote.\n\n- `is_clean_tree_at_start`: whether the working tree had no uncommitted changes when the session started.\n\n- `changed_file_count_at_start`: how many files had changes at session start.\n\n- `untracked_file_count_at_start`: how many files were not tracked by git at session start.\n\nThe code that reads and writes the format supports all four. The exporter pulls `_PROTO_git_remote_url` out of the extra metadata so that it does not end up in `additional_metadata`. However, the event it builds never sets `git_remote_url`, and nothing sets the three `*_at_start` fields.\n\n**Why**\n\nFor now these fields stay empty. They show where the event format is heading: once something starts filling them, events would carry your repository's remote address and how many uncommitted changes you had at session start, which is worth knowing if you care about what usage data contains.\n\n- Area: Telemetry\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}