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.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

--no-home-settings replaced by --forward-home-settings <true|false>

Use it now
Useful4 Signal3
Cloud Sessions Notable not in their notes

The hidden --no-home-settings flag becomes --forward-home-settings true or false, so you can force it on.

--forward-home-settings
What

The hidden cloud-session flag controlling whether this machine's settings go into the session is now tri-state. You can force forwarding on for one launch as well as off, rather than only opting out. The default is unchanged: with the flag absent, settings are still forwarded.

Details
  • Accepts true|false and 1|0; anything else is an error.
  • A forced value stands in for the stored choice for that launch only and is not saved.
  • Passing it without --cloud or --environment now errors with new wording.
  • The old --no-home-settings spelling is gone from the build.
Usage
claude --cloud --forward-home-settings false
Evidence

--forward-home-settings <true|false>, Error: --forward-home-settings says whether this machine's settings go into a cloud session; pass --cloud (a new session, or one to attach to) or --environment

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