{"version":"2.1.224","anchor":"team-memory-prompt-no-longer-explains-saving-when-nothing-ca","canonical_anchor":"team-memory-prompt-no-longer-explains-saving-when-nothing-ca","heading":"Team memory prompt no longer explains saving when nothing can be saved","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/team-memory-prompt-no-longer-explains-saving-when-nothing-ca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Team memory prompt no longer explains saving when nothing can be saved\n\nWith no writable team memory, Claude is no longer told how to save memories.\n\n**What**\n\nWhen your project has no writable team memory location, the instructions telling the model how to save memories are dropped from its prompt entirely, leaving only a statement that access is read-only.\n\n**Details**\n\n- The removed block is the \"## How to save memories\" section.\n- What remains: \"You have read-only access to team memory synced from your project. You cannot persist new memories in this session.\"\n- A shorter one-step variant of the save instructions is used when no index is required.\n\n**Evidence**\n\n`You have read-only access to team memory synced from your project. You cannot persist new memories in this session.`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}