{"version":"2.1.248","anchor":"output-shaping-helpers-for-bridge-environments","canonical_anchor":"output-shaping-helpers-for-bridge-environments","heading":"Output-shaping helpers for bridge environments","tier":"internal","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/output-shaping-helpers-for-bridge-environments","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Output-shaping helpers for bridge environments\n\nWhen frames leave your machine, MCP listings and repeated errors get trimmed down.\n\n**What**\n\nA 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.\n\n**Details**\n\n- Requires `CLAUDE_CODE_ENVIRONMENT_KIND=bridge` and a persisting transport. Inert outside bridge environments.\n\n**Evidence**\n\n`error_during_execution detail: `\n\n- Area: Remote Bridge\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}