{"version":"2.1.319","anchor":"remote-session-bridge-refuses-project-memory","canonical_anchor":"remote-session-bridge-refuses-project-memory","heading":"Remote-session bridge sessions now say why project memory is unavailable","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/remote-session-bridge-refuses-project-memory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Remote-session bridge sessions now say why project memory is unavailable\n\nWhen a session runs through the remote-session bridge, a tool now explains that project memory is not available there\n\n**What**\n\nProject memory is saved information about your project that Claude Code can read back. Some sessions run through the remote-session bridge, a link that connects a session to Claude Code running somewhere else. That bridge has no way to reach project memory.\n\nA tool asked for project memory in such a session now returns a clear error saying it does not serve project memory there, with the code `project_memory_no_route`.\n\n**Why**\n\nInstead of failing with no explanation, the tool tells you project memory is unavailable in bridge sessions.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}