{"version":"2.1.305","anchor":"config-sync-to-disk-skipped-when-a-non-default-host-is-used","canonical_anchor":"config-sync-to-disk-skipped-when-a-non-default-host-is-used","heading":"Feature settings from a non-default host are no longer saved to your config","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/config-sync-to-disk-skipped-when-a-non-default-host-is-used","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Feature settings from a non-default host are no longer saved to your config\n\nWhen Claude Code gets its remote feature settings from a non-default host, it no longer saves them to your global config\n\n**Unclear.** What makes Claude Code count a host as non-default is not stated.\n\n**What**\n\nClaude Code fetches some feature settings from a server and normally saves them to your global config file. When it used a non-default host for this, it now skips that save.\n\n**Why**\n\nFeature settings from a custom host no longer stay behind in your config after that session.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}