{"version":"2.1.223","anchor":"repl-registers-its-own-bridge-address-for-loop-detection","canonical_anchor":"repl-registers-its-own-bridge-address-for-loop-detection","heading":"REPL registers its own bridge address for loop detection","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/repl-registers-its-own-bridge-address-for-loop-detection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### REPL registers its own bridge address for loop detection\n\nYour session now advertises its own address so messages looping back to it get dropped instead of echoing.\n\n**What**\n\nThe main REPL now advertises its own address to the inter-Claude message layer so messages that hop back to this session can be recognized and dropped.\n\n**Details**\n\n- On mount it installs a self-address provider deriving a `bridge:`-prefixed address from the current bridge session id, and clears it on unmount.\n- Peer hop chains are now forwarded when sending files or messages to a cloud session.\n\n**Evidence**\n\n`bridge:`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}