{"version":"2.1.293","anchor":"account-memory-redaction-now-turns-on-only-when-memory-is-in","canonical_anchor":"account-memory-redaction-now-turns-on-only-when-memory-is-in","heading":"Hiding of account memory now depends on whether memory is in use","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/account-memory-redaction-now-turns-on-only-when-memory-is-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Hiding of account memory now depends on whether memory is in use\n\nClaude Code now hides account-memory content only when memory is in play, and treats it as in play when it cannot tell\n\n**What**\n\nAccount memory is information Claude keeps about you across conversations. Claude Code has a layer that hides that content by replacing it with a placeholder. Before, every message went through that layer the same way.\n\nIt now first checks whether account memory is in play:\n\n- When it is not, Claude Code takes a lighter path.\n\n- When it is, messages marked as memory are replaced with a placeholder.\n\n- When Claude Code cannot tell, or the check fails, it treats memory as in play.\n\nResponses from hooks (commands you configure to run at set moments) are now handled according to which kind of event they came from.\n\n**Why**\n\nThis narrows when memory content is hidden. If the signal for whether memory is in play is wrong, content could be hidden when it should not be, or shown when it should be hidden. Falling back to treating memory as in play leans toward hiding.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}