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.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Two new settings keys named: WSL settings inheritance and managed-source behaviour

Not switched on
Useful2 Signal4
Settings Notable

Two settings keys are named for WSL inheriting Windows settings and managed-source behaviour.

wslInheritsWindowsSettings and managedSourcesBehavior appear in a key list with no visible consumer.

wslInheritsWindowsSettingsmanagedSourcesBehavior
What

A list of settings keys now names managedSourcesBehavior and wslInheritsWindowsSettings, suggesting Windows settings can be inherited into WSL and that managed sources have configurable behaviour. What consumes the list, whether merge policy, migration or display, is not determined by the list itself. A separate list names enabledPlugins and extraKnownMarketplaces.

Evidence

["managedSourcesBehavior", "wslInheritsWindowsSettings"]

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