{"version":"2.1.301","anchor":"secret-scan-refusal-for-sessions-with-no-memory-folder","canonical_anchor":"secret-scan-refusal-for-sessions-with-no-memory-folder","heading":"Sessions with no memory folder block writing files that look like they hold secrets","tier":"notice","area":"Secret Scanning","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/secret-scan-refusal-for-sessions-with-no-memory-folder","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Sessions with no memory folder block writing files that look like they hold secrets\n\nWhen a session has no memory folder, Claude Code refuses to write any file whose content looks like it contains secrets such as passwords or keys\n\n**What**\n\nClaude Code scans what it is about to write for content that looks like secrets, such as passwords or access keys. This check used to cover only memory files, the notes Claude keeps for a team or an account.\n\nWhen a session has no memory folder, the check now covers every file. Any file write whose content contains possible secrets is refused. The message explains that the session has no memory folder, so every file it writes is checked as a memory file would be.\n\n**Why**\n\nIn sessions without local storage, such as some cloud sessions, writing secret-like content to any file is now blocked. If a write is refused there, look for passwords, keys or tokens in the content.\n\n- Area: Secret Scanning\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}