{"version":"2.1.246","anchor":"hook-approvals-can-be-sent-back-through-the-auto-mode-classi","canonical_anchor":"hook-approvals-can-be-sent-back-through-the-auto-mode-classi","heading":"Hook approvals can be sent back through the auto-mode classifier","tier":"soon","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/hook-approvals-can-be-sent-back-through-the-auto-mode-classi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Hook approvals can be sent back through the auto-mode classifier\n\nHook-approved tool calls could still be checked by the auto-mode classifier, but the flag is off.\n\n**What**\n\nWhen a hook approves a tool call that would run in auto mode, Claude Code can now stop treating that as final and run the call through the permission classifier anyway, with a note that the hook vouched for it. The branch sits behind a flag whose built-in fallback is off, so without a remote value hook approvals still bypass the classifier as before.\n\n**Details**\n\n- Gate: `tengu_virtual_knuth`, defaulting to off in the shipped code.\n- Logs `tengu_auto_mode_hook_allow_funneled` with tool name, whether it is MCP, and the hook's source bucketed to settings, plugin, skill or other.\n- Auto-mode decision events gained a field recording the hook vouch.\n- Debug output says the hook approved the tool use but auto mode requires classifier adjudication.\n\n**Evidence**\n\n`tengu_auto_mode_hook_allow_funneled`\n\n- Flag `tengu_virtual_knuth`: Not enough to say (read for one account on one subscription tier against v2.1.246; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: Permissions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}