{"version":"2.1.131","anchor":"clearer-api-authentication-error","canonical_anchor":"clearer-api-authentication-error","heading":"Clearer API Authentication Error","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.131\/e\/clearer-api-authentication-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.131","markdown":"### Clearer API Authentication Error\n\n**What**\n\nWhen the bundled Anthropic API client cannot resolve credentials, the error now says it expects either `apiKey` or `authToken`, instead of listing removed credential\/profile\/config options.\n\n**Usage**\n\n`ANTHROPIC_API_KEY=... claude` **Details** - This makes auth failures less misleading for users who hit lower-level API-client errors. - The new message points users toward API key or bearer-token authentication. - The previous message referenced `credentials`, `config`, and `profile`; those are no longer listed in the failure text. **Evidence** Authentication validation message changed (search for `\"Could not resolve authentication method. Expected either apiKey or authToken to be set\"`)."}