Remote managed settings check the stored copy's trust and signature

What

Remote managed settings are settings an administrator delivers to Claude Code from Anthropic's servers. Claude Code keeps a copy on disk, a cache, so it can use them between fetches.

• When fetching remote managed settings, Claude Code now judges the cached copy against a stored account and organization pin. Before, it only ran a background comparison of the cache contents.
• It verifies the signature on the live settings against a trusted signer. The check runs either "enforced" or in "shadow", where it is recorded without being acted on.
• The cache is rewritten differently when a signature is present, and the age of the cache is now reported.
• The sign-in loader gains state for a stored account, a pinned organization for the stored copy, a trust answer that starts as not_asked, a refusal, and a remembered sign-in.
• When the sign-in type is an API key but no usable key is available, the fetch now reports api_key_not_sent instead of no_auth_available. It is treated as a non-error where no_auth_available was, and grouped as client_no_credentials (no credentials).

Why

These checks make it harder for a tampered or stale settings cache to be applied. Diagnostics can also now tell API-key users apart from users who are not signed in at all.