{"version":"2.1.273","anchor":"repl-bridge-ignores-fork-display-frames-at-ingress","canonical_anchor":"repl-bridge-ignores-fork-display-frames-at-ingress","heading":"REPL bridge ignores fork display frames at ingress","tier":"internal","area":"REPL","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/repl-bridge-ignores-fork-display-frames-at-ingress","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### REPL bridge ignores fork display frames at ingress\n\nClaude Code's internal message bridge now ignores certain 'fork display frame' messages before processing them\n\n**Unclear.** What a 'fork display frame' is and what user-visible situation triggers one isn't stated; a related gate, `tengu_bridge_message_received`, hasn't been read for this site's account.\n\n**What**\n\nClaude Code has an internal bridge that receives messages for its interactive session (REPL). It now checks incoming messages early and, if a message is identified as a 'fork display frame', logs 'Ignoring fork display frame at ingress' and drops it immediately, before the usual de-duplication and telemetry logic runs.\n\n**Why**\n\nThis stops a particular kind of internal display message from being processed as if it were a regular user message.\n\n- Area: REPL\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}