{"version":"2.1.285","anchor":"org-memory-writes-refused-outside-the-required-session-kind","canonical_anchor":"org-memory-writes-refused-outside-the-required-session-kind","heading":"Organization memory writes are refused in unsupported kinds of session","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/org-memory-writes-refused-outside-the-required-session-kind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Organization memory writes are refused in unsupported kinds of session\n\nTurning on writes to organization memory is now refused unless the session is of a supported kind\n\n**Unclear.** It is not clear which kinds of session are allowed to write.\n\n**What**\n\nOrganization memory is shared memory that Claude Code can read and write across your organization's projects. Turning on writes to it now fails if the current session is not of a supported kind. Choosing a memory selection that would turn on writes in such a session is refused too. Before, the only refusals were for identity, remotely controlled settings, and reading being switched off.\n\n**Why**\n\nWriting to synced project memory is now limited to certain kinds of session, so in other sessions Claude Code can still read that memory but cannot change it.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}