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.223 Home All releases olderv2.1.222 v2.1.224newer

Host-orchestrated env var protection is case-insensitive

You'll notice
Useful3 Signal0
Windows

On Windows, differently-cased environment variable names can no longer override ones the host has claimed.

What

Environment variables claimed by the host can no longer be overridden by a differently-cased key, which mattered on Windows where env var names are case-insensitive.

Details
  • The claimed set is built by uppercasing the keys of process.env.
  • The filter that strips settings-provided env compares with .toUpperCase().
  • The guard that drops lower-trust redirects does the same.
Evidence

if (!uhr.has(r.toUpperCase())) t[r] = n;

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