{"version":"2.1.242","anchor":"forwarded-hook-bridge-for-cloud-sessions-behind-an-unresolve","canonical_anchor":"forwarded-hook-bridge-for-cloud-sessions-behind-an-unresolve","heading":"Forwarded-hook bridge for cloud sessions, behind an unresolved condition","tier":"soon","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/forwarded-hook-bridge-for-cloud-sessions-behind-an-unresolve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Forwarded-hook bridge for cloud sessions, behind an unresolved condition\n\nA bridge answering a cloud session's hooks on your machine is built behind an unresolved condition.\n\n**What**\n\nA new component wires a cloud session's hooks back to your machine, so hook callbacks raised remotely can be answered and released locally. It is constructed at exactly one place, and that place returns nothing unless the session is not view-only and a second condition holds.\n\n**Details**\n\n- The bridge registers callbacks for a forwarded hook firing and for one being cancelled, backed by the session manager's respond and release operations, and re-registers on stream connect, worker init, settings change and consent.\n- The condition at the call site is a bare function call. The only declaration of that name in the file returns false unconditionally, but this bundle reuses the same short names for different functions across chunks, so the file alone does not establish which one is in scope there.\n\n**Evidence**\n\n`onForwardedHookCallback`\n\n- Area: Hooks\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}