Two 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.
Where 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.
tengu_bridge_child_tool_diff Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.269: off
Read once, for one account on one subscription tier, against v2.1.269. It isn't a statement about your account. What a flag value here can and cannot tell you
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
| `CLAUDE_CODE_REMOTE_SESSION_ID` | Session ID in the tagged `cse_...` form. This is the same session the [lifecycle hooks](#lifecycle-hooks) see as `CLAUDE_RUNNER_SESSION_ID` in `session_...` form; the UUID variables match across both, an…self-hosted-environments-configuration see the edit
* **No cloud-only scoping**: hooks run in both local and cloud sessions. To skip local execution, exit early unless the `CLAUDE_CODE_REMOTE` environment variable is `true`, the way the [dependency install script](#install-dependencies-with…cloud-environments see the edit
A small documentation edit on Configure cloud environments touched a line naming CLAUDE_CODE_REMOTE after this was published.
New in this build: tengu_bridge_child_tool_diff