Claude Code v2.1.221 ·
Chrome bridge gains an activity-observer hook, not wired up
The Chrome bridge can report browser tool activity to an observer, but nothing supplies one yet.
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Chrome & BrowserArea: what it touches
In DevelopmentKind: in v2.1.221,
In DevelopmentSection of the release
Browser activity observer hooks around tool calls exist, but no consumer is wired up.
What
The bridge calls optional observer callbacks around tool calls, but nothing in this build supplies the observer.
Details
- Calls optional onBeforeToolCall and onToolResult on a context-supplied observer.
- Guarded by try/catch with a debug log if the observer throws.
- context.browserActivityObserver is never set in this build, so this is plumbing for a future consumer.
Evidence
browserActivityObserver
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.221 →
