{"version":"2.1.268","anchor":"hook-telemetry-span-changes-shape-in-remote-ccr-sessions","canonical_anchor":"hook-telemetry-span-changes-shape-in-remote-ccr-sessions","heading":"Hook telemetry span changes shape in remote (CCR) sessions","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/hook-telemetry-span-changes-shape-in-remote-ccr-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Hook telemetry span changes shape in remote (CCR) sessions\n\nHook telemetry looks different in remote (CCR) sessions, dropping hook_definitions and using the raw event name\n\n**What**\n\nIn 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.\n\n**Why**\n\nThis 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.\n\n- Area: Telemetry\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}