{"version":"2.1.319","anchor":"bridge-bridge-refusals-are-remembered-for-the-process","canonical_anchor":"bridge-bridge-refusals-are-remembered-for-the-process","heading":"A final bridge refusal is now remembered for the rest of the process","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/bridge-bridge-refusals-are-remembered-for-the-process","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### A final bridge refusal is now remembered for the rest of the process\n\nAfter a bridge request is refused for good, Claude Code stops asking again and reuses that refusal until it restarts\n\n**What**\n\nWhen the server gives a final refusal to a bridge request for a session, Claude Code now remembers it for as long as the program keeps running. Later bridge requests for that session are not sent again; they return the earlier refusal, and the log notes it was refused for good earlier in this process.\n\nRestoring an archived session behaves the same way and reports it as gone, with status 403. Before, every request asked the server again.\n\n**Why**\n\nThis stops Claude Code from sending the same failing request over and over. Restarting Claude Code clears the remembered refusal.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}