{"version":"2.1.232","anchor":"claude-plugin-failures-no-longer-lose-their-telemetry-on-exi","canonical_anchor":"claude-plugin-failures-no-longer-lose-their-telemetry-on-exi","heading":"claude plugin failures no longer lose their telemetry on exit","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/claude-plugin-failures-no-longer-lose-their-telemetry-on-exi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### `claude plugin` failures no longer lose their telemetry on exit\n\nFailed plugin commands now flush their analytics before exiting instead of dropping the event.\n\n**What**\n\nThe shared failure handler for `claude plugin` subcommands now waits for analytics to flush before exiting with code 1. Previously the process exited immediately and the `tengu_plugin_command_failed` event, along with a refused install source event, could be dropped.\n\n**Details**\n\n- The flush races pending tasks against 200 ms, then first-party event logging, Datadog and error tracking against 500 ms.\n- The install and uninstall paths now await the handler instead of calling it and moving on.\n\n**Evidence**\n\n`tengu_plugin_command_failed`, `flushAnalyticsSinks: () => TIe`\n\n- Area: Plugins\n- Names: `claude plugin`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}