{"version":"2.1.225","anchor":"device-bridge-lifecycle-telemetry","canonical_anchor":"device-bridge-lifecycle-telemetry","heading":"Device bridge lifecycle telemetry","tier":"soon","area":"Device Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/device-bridge-lifecycle-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Device bridge lifecycle telemetry\n\nThe device bridge reports its whole connection lifecycle, but none of it fires yet.\n\n**What**\n\nThe bridge reports its full connection lifecycle, gated the same way as the bridge itself, so none of it fires in this build unless `tengu_violin_wood` is on.\n\n**Details**\n\n- events: `tengu_device_bridge_started`, `_stopped`, `_skipped` (with reasons `missing_org` and `missing_account`), `_start_failed`, `_connected`, `_rejected`, `_closed`, `_connect_failed`, `_pong_timeout`, `_reconnect_exhausted` and `_heartbeat_unsupported`\n- the connected event records the protocol version plus negotiated `hb_interval_ms`, `staleness_ms` and `rpc_timeout_ms`\n- repeated transport failures are de-duplicated before being reported\n\n**Evidence**\n\n`tengu_device_bridge_heartbeat_unsupported`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.225; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Device Bridge\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}