Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.273 ·

REPL bridge ignores fork display frames at ingress

Claude Code's internal message bridge now ignores certain 'fork display frame' messages before processing them

Under the hood Bug Fixes
JSON All of v2.1.273
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
REPLArea: what it touches
Bug FixesKind: in v2.1.273,
Bug FixesSection of the release

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.

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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat a 'fork display frame' is and what user-visible situation triggers one isn't stated; a related gate, `tengu_bridge_message_received`…

See this entry in the whole of v2.1.273 →

Feedback