{"version":"2.1.224","anchor":"repl-bridge-survives-clear-instead-of-dropping","canonical_anchor":"repl-bridge-survives-clear-instead-of-dropping","heading":"REPL bridge survives \/clear instead of dropping","tier":"notice","area":"Editor Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/repl-bridge-survives-clear-instead-of-dropping","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### REPL bridge survives `\/clear` instead of dropping\n\nRunning \/clear no longer disconnects the editor bridge; it follows you onto the new session.\n\n**What**\n\nClearing the conversation no longer tears down the REPL bridge. The bridge now repoints onto the new session, carrying its session id, last sequence number, dialog kinds and grouping id, and flags that history should not be backfilled.\n\n**Details**\n\n- It also subscribes to reset, resume and spare-claim transitions.\n- Archiving the old session changed from an immediate call to a deferred, error-logged one that can be cancelled.\n- New telemetry records when the bridge disables itself automatically (`tengu_bridge_repl_auto_disabled`) and when a compaction happens while it is disabled.\n- Queued SDK events are forwarded with their own error logging rather than being lost silently.\n\n**Evidence**\n\n`tengu_bridge_repl_auto_disabled`\n\n- Area: Editor Bridge\n- Names: `\/clear`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}