{"version":"2.1.246","anchor":"no-home-settings-replaced-by-forward-home-settings-true-fals","canonical_anchor":"no-home-settings-replaced-by-forward-home-settings-true-fals","heading":"--no-home-settings replaced by --forward-home-settings <true|false>","tier":"use","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/no-home-settings-replaced-by-forward-home-settings-true-fals","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### `--no-home-settings` replaced by `--forward-home-settings <true|false>`\n\nThe hidden --no-home-settings flag becomes --forward-home-settings true or false, so you can force it on.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Accepts `true|false` and `1|0`; anything else is an error.\n- A forced value stands in for the stored choice for that launch only and is not saved.\n- Passing it without `--cloud` or `--environment` now errors with new wording.\n- The old `--no-home-settings` spelling is gone from the build.\n\n**Usage**\n\n`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`\n\n- Area: Cloud Sessions\n- Names: `--forward-home-settings`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}