{"version":"2.1.311","anchor":"account-memory-withdrawal-check-in-teleport-relay","canonical_anchor":"account-memory-withdrawal-check-in-teleport-relay","heading":"Remote sessions stop using account memory when it is withdrawn or withheld","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/account-memory-withdrawal-check-in-teleport-relay","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Remote sessions stop using account memory when it is withdrawn or withheld\n\nThe teleport relay now falls back to standard behaviour when account memory is withdrawn or withheld, and treats a failed check as withdrawn\n\n**What**\n\nThe teleport relay, which Claude Code uses for remote sessions, now checks whether account memory is withdrawn or withheld. When it is, the relay reverts to standard behaviour and requests skip the relay. Claude Code logs: \"teleport relay: account memory is withdrawn or withheld - reverting to standard behavior\".\n\nIf the check itself fails, Claude Code treats the memory as withdrawn and logs that the check failed.\n\nThe relay also now handles request bodies sent as raw binary data.\n\n**Why**\n\nMemory now fails closed in remote sessions. If Claude Code cannot confirm that account memory is available, it does not use it.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}