{"version":"2.1.265","anchor":"permission-check-pipeline-gained-a-pre-hook-adjustment-step","canonical_anchor":"permission-check-pipeline-gained-a-pre-hook-adjustment-step","heading":"Permission-check pipeline gained a pre-hook adjustment step (uot) before deny\/ask evaluation","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/permission-check-pipeline-gained-a-pre-hook-adjustment-step","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Permission-check pipeline gained a pre-hook adjustment step (uot) before deny\/ask evaluation\n\nTool permission checks now let a hook adjust the decision before deny\/ask logic runs\n\n**What**\n\nBefore Claude Code decides whether to deny or ask about a tool call, both of its permission-decision code paths now run a new step that lets a hook (custom code that runs at a specific point in Claude Code's process) inspect and potentially adjust the in-progress permission decision before the deny or ask branches are evaluated.\n\n**Why**\n\nThis opens a point where custom hook logic can influence permission outcomes earlier in the pipeline, ahead of the standard deny\/ask evaluation.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}