{"version":"2.1.221","anchor":"chrome-bridge-gains-an-activity-observer-hook-not-wired-up","canonical_anchor":"chrome-bridge-gains-an-activity-observer-hook-not-wired-up","heading":"Chrome bridge gains an activity-observer hook, not wired up","tier":"internal","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/chrome-bridge-gains-an-activity-observer-hook-not-wired-up","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Chrome bridge gains an activity-observer hook, not wired up\n\nThe Chrome bridge can report browser tool activity to an observer, but nothing supplies one yet.\n\n**What**\n\nThe bridge calls optional observer callbacks around tool calls, but nothing in this build supplies the observer.\n\n**Details**\n\n- Calls optional onBeforeToolCall and onToolResult on a context-supplied observer.\n- Guarded by try\/catch with a debug log if the observer throws.\n- context.browserActivityObserver is never set in this build, so this is plumbing for a future consumer.\n\n**Evidence**\n\n`browserActivityObserver`\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}