{"version":"2.1.318","anchor":"edit-diff-watcher-records-a-usage-marker","canonical_anchor":"edit-diff-watcher-records-a-usage-marker","heading":"Per-session usage counters for edit-diff watching and relay traffic","tier":"internal","area":"Diffs","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/edit-diff-watcher-records-a-usage-marker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Per-session usage counters for edit-diff watching and relay traffic\n\nClaude Code now counts edit-diff watcher events and relay connections, dials and bytes for each session\n\n**What**\n\nClaude Code now keeps a table of usage counts for each session. A session is one conversation with Claude from start to finish.\n\n- `edit_diff_watch_events` and `edit_diff_watch_dirs` count activity of the file watcher, which notices when files change so edits can be shown as differences. The watcher now counts each event it handles.\n\n- `relay_connections`, `relay_dials` and `relay_bytes` count relay traffic. Uploads sent through the relay now add to `relay_bytes`.\n\n**Why**\n\nThese counts are internal bookkeeping. They do not change how file watching or the relay behave for you.\n\n- Area: Diffs\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}