What
In a remote Claude Code session (CLAUDE_CODE_REMOTE) that has no bridge carrier, the telemetry span recorded for a hook run now uses the raw event name in place of the resolved hook_name attribute, and omits the hook_definitions field entirely. hook_definitions is now only included when a separate condition (Ol()) is true and the session is not this kind of remote session.
Why
This changes what detail is available in hook-related telemetry for remote sessions specifically, which matters for anyone inspecting or debugging hook behavior through that telemetry.
Names in the bundleCLAUDE_CODE_REMOTE
Documented inclaude-code/agent-sdk/typescript
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.
Confirmed since
Anthropic's documentation has since written up CLAUDE_CODE_REMOTE, on Customize sessions in self-hosted environments.
| `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
Added since
A small documentation edit on Configure cloud environments touched a line naming CLAUDE_CODE_REMOTE after this was published.
* **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
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Configure cloud environments touched a line naming CLAUDE_CODE_REMOTE after this was published.