{"version":"2.1.292","anchor":"tool-check-hooks-can-no-longer-override-tools-that-require-t","canonical_anchor":"tool-check-hooks-can-no-longer-override-tools-that-require-t","heading":"Plugin checks can no longer approve tools that need your input","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/tool-check-hooks-can-no-longer-override-tools-that-require-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Plugin checks can no longer approve tools that need your input\n\nWhen a tool needs you to interact with it, Claude Code's own permission decision now overrides a plugin's `tool.check` hook\n\n**What**\n\nPlugins can add a `tool.check` hook. A hook is a piece of code that runs at a set moment, and this one runs before Claude uses a tool and can give a verdict on whether the tool may run. When the tool requires you to interact with it, Claude Code now keeps its own decision and holds back the hook's verdict.\n\nPreviously, the hook's verdict was held back only for MCP tool calls in remote sessions. MCP tools come from outside programs connected to Claude Code.\n\n**Why**\n\nA plugin can no longer approve a tool on your behalf when that tool is meant to wait for you.\n\n- Area: Hooks\n- Names: `tool.check`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}