{"version":"2.1.293","anchor":"prefer1mcontext-marked-hot-applied-for-remote-policy","canonical_anchor":"prefer1mcontext-marked-hot-applied-for-remote-policy","heading":"Remote policy changes to the 1M-context preference marked to apply without a restart","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/prefer1mcontext-marked-hot-applied-for-remote-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Remote policy changes to the 1M-context preference marked to apply without a restart\n\n`modelPrefer1mContext` and `disableConfigDeprecationWarnings` are now marked to take effect as soon as a remote policy changes them\n\n**Unclear.** It is not confirmed that the hot-applied mark makes these changes take effect without a restart.\n\n**What**\n\nThe setting that makes the model picker prefer the 1M-context version of a model (`modelPrefer1mContext`) is now marked as hot-applied for remote policy. Remote policy means settings an organization sends to Claude Code from a server, and hot-applied means a change is meant to take effect while Claude Code is running. The managed setting `disableConfigDeprecationWarnings` carries the same mark.\n\n**Why**\n\nWhen an administrator changes either setting through remote policy, users may no longer need to restart Claude Code for the change to apply.\n\n- Area: Managed Settings\n- Names: `modelPrefer1mContext`, `disableConfigDeprecationWarnings`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}