When frames leave your machine, MCP listings and repeated errors get trimmed down.
What's wrong with this entry?
A new module tracks, per connection, which transport is active and whether it carries frames off the machine, and offers a way to mark a transport as local. A predicate combining bridge mode with that flag drives the trimming applied elsewhere: MCP entries reduced to name and status, lists emptied, and multiple execution errors collapsed into one entry with the rest logged.
- Requires
CLAUDE_CODE_ENVIRONMENT_KIND=bridgeand a persisting transport. Inert outside bridge environments.
error_during_execution detail:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge
-
v2.1.236
Remote bridge waits for the disconnect notice, and an inbox fetch that is always off
Both mention bridge
-
v2.1.236
Bridge shuts down cleanly on SIGHUP
Both mention bridge