{"version":"2.1.238","anchor":"working-out-where-an-auth-token-came-from-is-now-asynchronou","canonical_anchor":"working-out-where-an-auth-token-came-from-is-now-asynchronou","heading":"Working out where an auth token came from is now asynchronous","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/working-out-where-an-auth-token-came-from-is-now-asynchronou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Working out where an auth token came from is now asynchronous\n\nFiguring out where your auth token came from is now asynchronous and returns both token forms together.\n\n**What**\n\nThe helper that classified a token as coming from the credential store, the environment or a file descriptor no longer reads the store synchronously; callers await it and it returns the bearer token and file-descriptor token together. The organization UUID check and one startup task became asynchronous to match.\n\n**Evidence**\n\n`CLAUDE_CODE_ORGANIZATION_UUID`\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}