{"version":"2.1.265","anchor":"new-explicit-messages-for-project-memory-being-unreachable-v","canonical_anchor":"new-explicit-messages-for-project-memory-being-unreachable-v","heading":"New explicit messages for project memory being unreachable via the remote-session bridge","tier":"notice","area":"Project Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-explicit-messages-for-project-memory-being-unreachable-v","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New explicit messages for project memory being unreachable via the remote-session bridge\n\nClearer error messages explain when project memory isn't reachable over a remote session or is turned off\n\n**What**\n\nClaude Code now shows explicit messages when project memory can't be used. One message explains that project memory tools throw an error when running through the remote-session bridge, because that bridge has no memory access. A separate message explains when memory access is simply turned off or the server doesn't yet support it, noting that this is re-checked the next time context is rebuilt or a new session starts.\n\n**Why**\n\nThese messages make it clear why project memory isn't working in a given situation, distinguishing a structural limitation (remote-session bridge) from a temporary or configuration-based one (access off or not yet supported), and confirming it will be re-checked later rather than staying broken indefinitely.\n\n- Area: Project Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}