New startup telemetry tracks managed-config readiness and an optional live identity check
A new telemetry event, tengu_managed_config_ready, records when Claude Code has finished resolving both its 'settings' and 'policy' managed-configuration sources (used by organizations to centrally control Claude Code) along with their permission checks. It captures which source was used, whether the result came from cache, and how long fetching and settling took.
Alongside it, a new check can verify that the organization or account ID implied by the authentication token actually matches, but this only runs for first-party (Anthropic) authentication.
This is groundwork for diagnosing and validating managed-configuration setups and account identity, though whether it's active depends on server-side settings not visible from the client.
Whether the `tengu_brass_lantern` gate or the live-identity check is switched on for any account is not known; no reading of either gate has…