Hook telemetry looks different in remote (CCR) sessions, dropping hook_definitions and using the raw event name
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.
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.
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.
* **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.