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.7 Home All releases olderv2.1.6 v2.1.8newer
Claude Code v2.1.7

Chrome Browser Skill

Feature flag
tengu_chrome_auto_enable On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: off · compiled default in v2.1.7: no gate table built for this version

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.7. It isn't a statement about your account. What a flag value here can and cannot tell you

What

Added a new claude-in-chrome skill that enables browser automation tools via the Skill tool.

Details
  • Provides comprehensive guidance for browser automation including GIF recording, console log debugging, and dialog handling
  • Controlled by tengu_chrome_auto_enable feature flag
  • Must invoke skill before using mcp__claude-in-chrome__* tools
  • Includes instructions for tab context management and session startup
Evidence

TI9() at line 516042 (skill registration, contains "claude-in-chrome")

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.7 →