{"version":"2.1.280","anchor":"the-main-system-prompt-in-the-reminder-read-empty-prompt-was","canonical_anchor":"the-main-system-prompt-in-the-reminder-read-empty-prompt-was","heading":"The main system prompt in the reminder-read-empty 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-read-empty-prompt-was","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### The main system prompt in the reminder-read-empty prompt was rewritten\n\nThe reminder-read-empty prompt was rewritten with guidance on leaving blocked parts of a task explicit\n\n**What**\n\nThe system prompt text used in the reminder-read-empty context (shown when a read turns up an empty file) was rewritten. The new wording says that if part of the task's scope is blocked or problematic, Claude should finish every other part in full and explicitly say what it left out and why, since scaling the work down is the user's call, not Claude's.\n\n**Why**\n\nThis tells Claude not to quietly drop or shrink part of a task when it hits a blocker on an empty file, but to complete everything else and flag the gap clearly.\n\n- Area: System Prompt\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}