GitHub Repo
Hermes Agent Community Reports Credential-Selection Bug That May Misuse Claude Code Token With Azure Configuration
On November 12, the Hermes Agent community reported that a particular Azure Foundry configuration can cause the credential resolver to select a local Claude Code OAuth token. The report includes an offline reproduction and a temporary workaround, but no verification of actual transmission or merged fix.

On November 12, the Hermes Agent GitHub community reported that a seemingly valid model configuration may pair the wrong endpoint and credential: when model.provider is set to anthropic, model.base_url points to Azure Foundry, and Claude Code credentials are stored locally, the resolver reportedly prioritizes the Claude Code OAuth token—even if the user has configured an Azure key. This could cause authentication failures and risk submitting a subscription credential to a non-Anthropic host. Issue report
The author traced the cause to the credential-resolution order: the code checks the credential pool before entering the branch that handles Azure specially; an earlier Azure check only examines a URL passed on the command line and misses model.base_url in the configuration file. As a result, even though the endpoint is changed to Foundry, the credential source may still follow the native Anthropic path. The author says the same behavior was reproduced on v0.22.2, v0.23.1, and the main branch. The tests disabled networking and only checked the resolver's return value, so they do not prove that a token was actually sent or misused. Reproduction and root-cause analysis
This also reveals a gap between the documentation and implementation. The official Hermes guide lists provider: anthropic with an Azure URL as an alternative setup and says it bypasses the Claude Code OAuth credential chain; the guide also provides a dedicated azure-foundry provider. Microsoft documentation says that Claude Code integration with Foundry authenticates using Microsoft Entra ID or a Foundry API key. Using the Anthropic message format does not mean the authentication source can also be reused directly. Hermes guide, Microsoft authentication documentation
The author later added that, on the current main branch, explicitly binding the endpoint and key in a providers: entry produces the correct result, but cases using only model.api_key or AZURE_ANTHROPIC_KEY still have problems. As of this check, the issue remains open and lists no related fix. Engineering teams should watch for follow-up tests that cover both configuration-file and command-line URLs, as well as credential-selection order when multiple credentials are stored locally. Any temporary workaround should also be verified against the specific version in use. Follow-up tests and status