{"version":"2.1.221","anchor":"new-telemetry-for-post-install-plugin-activation","canonical_anchor":"new-telemetry-for-post-install-plugin-activation","heading":"New telemetry for post-install plugin activation","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/new-telemetry-for-post-install-plugin-activation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### New telemetry for post-install plugin activation\n\nClaude now records whether a freshly installed plugin actually activated, and why it didn't.\n\n**What**\n\nThe in-session activation helper reports whether it managed to bring the plugin up and why not when it did not.\n\n**Details**\n\n- Emits `tengu_plugin_install_auto_activate` with `activated`, true when nothing blocked it, and a `reason` field on failure.\n- Separately records outcomes under the name \"plugin_install_auto_activate\" with reasons \"cache_impact\", \"refresh_failed\" and \"plugin_load_error\".\n- Fires wherever the install flow runs.\n\n**Evidence**\n\n`tengu_plugin_install_auto_activate`\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}