{"version":"2.1.269","anchor":"bridgedchild-session-tool-diffs-gated-behind-tengu-bridge-c","canonical_anchor":"bridgedchild-session-tool-diffs-gated-behind-tengu-bridge-c","heading":"Bridged\/child-session tool diffs gated behind tengu_bridge_child_tool_diff (default off)","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/bridgedchild-session-tool-diffs-gated-behind-tengu-bridge-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Bridged\/child-session tool diffs gated behind tengu_bridge_child_tool_diff (default off)\n\nNew tengu_bridge_child_tool_diff setting controls whether child-session file edits are shown as diffs to a parent session\n\n**What**\n\nTwo new functions decide whether a computed, git-style diff (a summary of changed lines) is attached to a write-tool result for background or child sessions. One function enables this either when the `CLAUDE_CODE_REMOTE` environment variable is set, or when an internal bridge\/child check is combined with a setting called `tengu_bridge_child_tool_diff`. The other function caps the diff size to 65536 bytes unless `CLAUDE_CODE_REMOTE` is set. When active, it logs a `tengu_tool_use_diff_computed` event.\n\n**Why**\n\nWhere enabled, this lets a coordinating parent session see a child agent's file edits as a readable diff instead of just the final file content, making it easier to review what a subagent actually changed.\n\n- Flag `tengu_bridge_child_tool_diff`: Not enough to say (read for one account on one subscription tier against v2.1.269; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: Sessions\n- Names: `tengu_bridge_child_tool_diff`, `CLAUDE_CODE_REMOTE`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}