{"version":"2.1.248","anchor":"remote-managed-settings-now-show-in-status-and-doctor-with-a","canonical_anchor":"remote-managed-settings-now-show-in-status-and-doctor-with-a","heading":"Remote managed settings now show in \/status and doctor, with a startup warning on failure","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-managed-settings-now-show-in-status-and-doctor-with-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote managed settings now show in \/status and doctor, with a startup warning on failure\n\n\/status and doctor now report remotely-published org settings, with a startup warning on failure.\n\n**What**\n\nSettings your organization publishes remotely now report their state. `\/status` adds a \"Managed settings (remote)\" row when something is wrong, `claude doctor` prints the resolved state or a \"checking\u2026\" line while a fetch is in flight, and a new startup notice appears when the fetch failed or fell back to a cached policy.\n\n**Details**\n\n- States render from fixed text such as `none configured for this organization` or `not fetched \u2014 ` plus a reason.\n- The notice carries the id `remote-managed-settings-failed`.\n- No flag, but whether a fetch is attempted at all depends on eligibility: it \"requires an Enterprise or Team subscription\" and is \"not available with a custom ANTHROPIC_BASE_URL\", and is also skipped for third-party providers, sandboxed entrypoints and pinned gateways.\n\n**Evidence**\n\n`Remote managed settings failed to load (`\n\n- Area: Managed Settings\n- Names: `\/status`, `claude doctor`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}