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.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Remote managed settings now show in /status and doctor, with a startup warning on failure

Use it now
Useful3 Signal3
Managed Settings

/status and doctor now report remotely-published org settings, with a startup warning on failure.

/statusclaude doctor
What

Settings 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…" line while a fetch is in flight, and a new startup notice appears when the fetch failed or fell back to a cached policy.

Details
  • States render from fixed text such as none configured for this organization or not fetched — plus a reason.
  • The notice carries the id remote-managed-settings-failed.
  • 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.
Evidence

Remote managed settings failed to load (

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