{"version":"2.1.273","anchor":"tengu-bridge-child-tool-diff-now-defaults-on-for-bridge-sess","canonical_anchor":"tengu-bridge-child-tool-diff-now-defaults-on-for-bridge-sess","heading":"Bridge sessions now default to computing tool-use diffs","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/tengu-bridge-child-tool-diff-now-defaults-on-for-bridge-sess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Bridge sessions now default to computing tool-use diffs\n\nRemote Control (bridge) sessions now compute and send tool-call diffs by default\n\n**Unclear.** Nothing has been read yet about whether the `tengu_bridge_child_tool_diff` setting is switched on for any account.\n\n**What** In a Remote Control (\"bridge\") session, Claude Code now defaults to computing a diff for tool calls like Write and Edit, so the change can be reported back over the bridge. This is controlled by the `tengu_bridge_child_tool_diff` setting, which is checked only when the session's environment is a bridge session (`CLAUDE_CODE_ENVIRONMENT_KIND === \"bridge\"`). Setting `CLAUDE_CODE_REMOTE` always forces this on regardless of that flag.\n\n**Why** Showing a diff for file-changing tool calls lets the Remote Control host display exactly what changed, without extra configuration.\n\n- Flag `tengu_bridge_child_tool_diff`: Not enough to say (read for one account on one subscription tier against v2.1.273; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Control\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}