{"version":"2.1.280","anchor":"tengu-init-telemetry-bug-fix-three-fields-were-reading-from","canonical_anchor":"tengu-init-telemetry-bug-fix-three-fields-were-reading-from","heading":"tengu_init telemetry bug fix: three fields were reading from an unrelated\/undefined variable","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/tengu-init-telemetry-bug-fix-three-fields-were-reading-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### tengu_init telemetry bug fix: three fields were reading from an unrelated\/undefined variable\n\nFixed a telemetry bug where three session-start fields were pulled from the wrong variable\n\n**What**\n\nIn the `tengu_init` telemetry event sent when a Claude Code session starts, three fields were being read from the wrong source. `lockfile_family`, `private_registry_host_class`, and `os_locked_toolchain` had been pulling their values from a variable that didn't match the one the rest of the payload used, so they weren't reflecting the same data as everything else in the event. The code now reads all three fields from the correct, consistent source.\n\n**Why**\n\nThis is an internal telemetry fix, not a user-facing feature. It means these three fields in session-start data should now report accurate values instead of coming from an unrelated variable.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}