{"version":"2.1.268","anchor":"tool-call-telemetry-now-suppresses-detailed-input-fields-in","canonical_anchor":"tool-call-telemetry-now-suppresses-detailed-input-fields-in","heading":"Tool-call telemetry now suppresses detailed input fields in some sessions","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/tool-call-telemetry-now-suppresses-detailed-input-fields-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Tool-call telemetry now suppresses detailed input fields in some sessions\n\nTool-call telemetry now skips file paths, commands, and skill\/subagent names in some sessions\n\n**Unclear.** What determines which sessions have these fields suppressed is not stated.\n\n**What**\n\nWhen Claude Code records telemetry for a tool call, it normally attaches detail fields like `file_path`, `full_command`, `skill_name`, and `subagent_type`. This now only happens when an additional check passes; in sessions where that check comes back true, none of these detailed fields are attached to the telemetry payload.\n\n**Why**\n\nThis means some sessions send less detailed tool-call telemetry than before, likely to avoid capturing sensitive details like file paths or command text in those cases.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}