{"version":"2.1.280","anchor":"the-main-system-prompt-in-the-reminder-hook-pretool-block-pr","canonical_anchor":"the-main-system-prompt-in-the-reminder-hook-pretool-block-pr","heading":"The main system prompt in the reminder-hook-pretool-block prompt was rewritten","tier":"internal","area":"System Prompt","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/the-main-system-prompt-in-the-reminder-hook-pretool-block-pr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### The main system prompt in the reminder-hook-pretool-block prompt was rewritten\n\nThe reminder-hook-pretool-block prompt was rewritten with new guidance on sticking to the requested scope of work\n\n**What**\n\nThe system prompt text used in the reminder-hook-pretool-block context (shown when a pre-tool-use hook blocks a tool call) was rewritten. The new wording instructs doing ordinary work as asked rather than acting on speculation about intent, treating the requested scope as the deliverable, using judgment on ambiguity, raising real problems in a sentence or two before continuing, and finishing the whole task rather than reporting completion early.\n\n**Why**\n\nThis shapes how Claude behaves when a hook has blocked one of its tool calls, pushing it to stay within the original request's scope and finish the task rather than narrowing, widening, or abandoning it.\n\n- Area: System Prompt\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}