Source Intelligence
Follow Discord

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.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

VS Code-owned sessions get their own settings defaultMode handling

You'll notice
Useful3 Signal0
Permissions

In VS Code sessions, unsafe default permission modes from settings are refused and fall back to normal.

Feature flag
tengu_harbor_willow Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.225: on

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.225. It isn't a statement about your account. What a flag value here can and cannot tell you

permissions.defaultModebypassPermissions
What

For sessions owned by the VS Code extension, permissions.defaultMode is read only from policy, flag and user settings, and unsafe values from settings are refused.

Details
  • bypassPermissions from settings is ignored unless the user has consented; a warning is printed to stderr and the mode falls back to default.
  • auto is ignored while the auto-mode circuit breaker is active.
  • The auto read additionally requires tengu_harbor_willow (fallback !1) or a meadow_lantern config value.
Evidence

tengu_settings_bypass_unconsented_noninteractive_ignored

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