{"version":"2.1.319","anchor":"memory-bridge-refusal-replaced-by-a-boolean-check","canonical_anchor":"memory-bridge-refusal-replaced-by-a-boolean-check","heading":"Project memory check in bridged remote sessions no longer raises an error","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/memory-bridge-refusal-replaced-by-a-boolean-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Project memory check in bridged remote sessions no longer raises an error\n\nThe check for project memory in sessions reached through the remote bridge now gives a yes or no answer instead of stopping with an error\n\n**Unclear.** It is not clear whether project memory now works in bridged remote sessions or is still unavailable there.\n\n**What**\n\nProject memory is the saved notes Claude Code keeps about a project. When a session is reached through the remote session bridge, a check used to stop with the error \"Project memory is not available in this session\". That check now gives a yes or no answer instead.\n\n**Why**\n\nProject memory may behave differently in remote sessions as a result.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}