Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.221 Home All releases olderv2.1.220 v2.1.222newer

Chrome bridge gains an activity-observer hook, not wired up

Under the hood
Useful1 Signal2
Chrome & Browser

The Chrome bridge can report browser tool activity to an observer, but nothing supplies one yet.

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.221 →