{"version":"2.1.305","anchor":"hosted-hooks-module-next-now-validates-floors","canonical_anchor":"hosted-hooks-module-next-now-validates-floors","heading":"Plugin hooks modules now have the floors they hand back checked","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/hosted-hooks-module-next-now-validates-floors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Plugin hooks modules now have the floors they hand back checked\n\nWhen a plugin hooks module calls next(), Claude Code now checks the floors handed back and refuses ones the plugins cannot reach\n\n**What**\n\nA hooks module is a plugin file that reacts to Claude Code events, and it can pass control on with `next()`. Claude Code now checks the floors handed to `next()` against those that a `next.to` call in the same plugins could lead to. If they do not match, the call is refused with \"next refused: the floors handed back are not ones a next.to of these plugins leaves (host rule)\". Before, these were passed through without a check.\n\n**Why**\n\nPlugin authors using `next.to` face stricter checks, and a hooks module that hands back unexpected floors now fails.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}