{"version":"2.1.323","anchor":"hooks-worker-crash-messages-withheld-output-no-longer-stays","canonical_anchor":"hooks-worker-crash-messages-withheld-output-no-longer-stays","heading":"Output held back by a crashed plugin hook is now released","tier":"notice","area":"Plugin Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/hooks-worker-crash-messages-withheld-output-no-longer-stays","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Output held back by a crashed plugin hook is now released\n\nWhen a plugin crashes the hooks worker, the output it was holding back is released instead of staying held\n\n**What**\n\nHooks are commands that plugins can run automatically at set points while Claude Code works. They run in a separate background process called the hooks worker.\n\nWhen a plugin crashes that worker, Claude Code shows a notice. The notice now says that what was held back \"is no longer withheld\". Before, it said the output stayed held back until the plugin was reloaded or disabled. The notice is also now reported in one more place.\n\n**Why**\n\nThe output really is released now, so a crashing plugin no longer keeps things blocked until you reload or disable it.\n\n- Area: Plugin Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}