{"version":"2.1.319","anchor":"project-doc-savedelete-needs-human-approval-when-tainted-by","canonical_anchor":"project-doc-savedelete-needs-human-approval-when-tainted-by","heading":"Saving or deleting a project doc may now need your approval","tier":"notice","area":"Project Docs","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/project-doc-savedelete-needs-human-approval-when-tainted-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Saving or deleting a project doc may now need your approval\n\nSaving or deleting a project doc now asks a person to approve it when other people's text may have reached the model in that turn\n\n**Unclear.** Which permission modes skip this approval is not stated.\n\n**What**\n\nProject docs are documents Claude Code keeps as knowledge about your project. Saving or deleting one used to be allowed without asking. Now Claude Code asks for approval when text from other people may have reached the model during the turn. The prompt says: \"A save or delete of a project doc. It needs a person's approval, because text from other people may have reached you in this turn.\"\n\nAn always-allow rule cannot approve this request, so a person has to answer it each time. In some permission modes the check is skipped.\n\n**Why**\n\nText from other people, such as a web page or a message, could contain hidden instructions telling the model to change your project knowledge. This is called prompt injection. Asking a person first stops that text from quietly saving or deleting project docs.\n\n- Area: Project Docs\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}