Under the hood
Claude Code's internal message bridge now ignores certain 'fork display frame' messages before processing them
What
Claude 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.
Why
This stops a particular kind of internal display message from being processed as if it were a regular user message.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What a 'fork display frame' is and what user-visible situation triggers one isn't stated; a related gate, `tengu_bridge_message_received`…