{"version":"2.1.290","anchor":"remote-bridge-fatal-errors-can-be-marked-suppressible","canonical_anchor":"remote-bridge-fatal-errors-can-be-marked-suppressible","heading":"Some fatal errors in the remote connection can now be marked as ones to hide","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-bridge-fatal-errors-can-be-marked-suppressible","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Some fatal errors in the remote connection can now be marked as ones to hide\n\nFatal errors from Claude Code's remote connection can now carry a mark saying they may be hidden from you\n\n**Unclear.** It is not clear which errors get this mark or what decides it.\n\n**What**\n\nWhen Claude Code's remote connection (the link that relays a session between Claude Code and another place it is controlled from) hits an error it cannot recover from, that error can now carry an extra mark saying it is suppressible. A suppressible error is one that does not have to be shown. Fatal errors in this connection had no such mark before.\n\n**Why**\n\nIn practice, some fatal errors from the remote connection may no longer appear on screen even though the connection still stopped. If a remote session ends without a message, this may be the reason.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}