{"version":"2.1.323","anchor":"remote-bridge-identity-probe-and-ca-cert-error-handling","canonical_anchor":"remote-bridge-identity-probe-and-ca-cert-error-handling","heading":"Remote bridge checks identity and no longer fails on a certificate check error","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-bridge-identity-probe-and-ca-cert-error-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote bridge checks identity and no longer fails on a certificate check error\n\nThe remote bridge now runs an identity check, and a failed certificate check falls back to parsing the certificates\n\n**Unclear.** What the new identity check verifies, and whether a user would ever notice it, is not clear.\n\n**What**\n\nThe remote bridge is the connection Claude Code uses for remote sessions. One step in it used to just build an address. It now runs an identity check first.\n\nAt startup, Claude Code compares security certificates against a table of known trusted roots. If that comparison throws an error, Claude Code now logs the error and parses the certificates instead. Before, the error was not caught.\n\n**Why**\n\nBoth changes make the remote bridge and the secure-connection setup at startup harder to break.\n\n- Flag `tengu_bridge_requires_action_details`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.323; this account: on, anonymous baseline: on, compiled default: on) 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: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}