{"version":"2.1.299","anchor":"installed-mods-telemetry-on-sdk-results-and-crashes","canonical_anchor":"installed-mods-telemetry-on-sdk-results-and-crashes","heading":"SDK result and crash reports now count installed plugin mods","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/installed-mods-telemetry-on-sdk-results-and-crashes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### SDK result and crash reports now count installed plugin mods\n\nUsage reports at the end of SDK and print-mode runs, and on crashes, now include how many plugin mods were installed\n\n**What**\n\nWhen Claude Code runs without its interactive screen (through the SDK, the software development kit for building on Claude Code, or in print mode), it sends a usage report when a run finishes and another if the session crashes. Both reports now include `installed_mods`, the highest number of plugin mods seen during the session. Plugins are add-on packages that extend Claude Code, and mods are the pieces they install.\n\nA turn that fails before it gets to run now also produces an error result, instead of ending without one.\n\n**Why**\n\nThe new count shows how widely the plugin system is used in these sessions. Nothing changes in what you see or do.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}