{"version":"2.1.234","anchor":"device-bridge-is-skipped-when-the-host-account-does-not-matc","canonical_anchor":"device-bridge-is-skipped-when-the-host-account-does-not-matc","heading":"Device bridge is skipped when the host account does not match","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/device-bridge-is-skipped-when-the-host-account-does-not-matc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Device bridge is skipped when the host account does not match\n\nThe device bridge is skipped entirely when the host's account UUID doesn't match the stored one.\n\n**What**\n\nThe device bridge now compares the stored account UUID against a host-supplied `CLAUDE_CODE_ACCOUNT_UUID` and skips the bridge entirely if they differ, instead of proceeding. The environment value is only honoured when it arrived from a trusted env or file-descriptor source.\n\n**Details**\n\n- Account resolution moved into one helper returning resolved, missing, or mismatch.\n- `tengu_device_bridge_skipped` now carries an `account_mismatch` field alongside the existing missing-org and missing-account fields.\n- A debug line names the resolution status when the bridge is skipped.\n\n**Evidence**\n\n`account_mismatch`\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_ACCOUNT_UUID`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}