{"version":"2.1.304","anchor":"plugin-hook-bypass-is-now-logged-once-per-session-and-rate-l","canonical_anchor":"plugin-hook-bypass-is-now-logged-once-per-session-and-rate-l","heading":"Repeated plugin hook bypass messages are logged once, then summarized","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/plugin-hook-bypass-is-now-logged-once-per-session-and-rate-l","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Repeated plugin hook bypass messages are logged once, then summarized\n\nWhen a plugin hook is passed over for a higher-priority one, the debug log now notes it once and later gives a count of repeats\n\n**What**\n\nPlugins can provide hooks, which are actions that run automatically at set points. When one plugin's hook is passed over because a higher-priority source handles the same event, Claude Code writes a line to its debug log. That line used to be written every time.\n\nIt is now written once. Later repeats are counted, and after a while the log shows a summary saying how many more times it happened in the last few seconds. Claude Code also records that the hook was passed over.\n\n**Why**\n\nDebug logs are much shorter and easier to read when a plugin hook is bypassed many times in one session.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}