NousResearch/hermes-agent

Anthropic credential leak fix: env token sent to third-party endpoints

Cluster 105774. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #107978 on 11 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #107978. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #107978. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #107978, then check it covers your case.

Read #107978 Pick up a Lab task

These items address a bug where the ANTHROPIC_AUTH_TOKEN environment variable could be forwarded to non-Anthropic compatible endpoints alongside an api_key, resulting in unintended dual-credential exposure. The fixes ensure only one credential is sent and that the env-derived token is cleared on api-key-style clients.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#107978 fix(anthropic): a client sends exactly one credential, on copies too (#105774, salvage #105778)

merged to main

files: agent/anthropic_adapter.py, contributors/emails/[email protected], tests/agent/test_anthropic_adapter.py, tests/agent/test_anthropic_client_auth.py, tests/agent/test_auxiliary_client_azure_foundry.py, tests/agent/test_nous_portal_anthropic_wire.py

2 PRs closed without merging

From the close comments: duplicate 1 · stale or abandoned 1

#105778 fix(anthropic): clear SDK env-derived auth_token on api-key-style clients · stale or abandoned
#105819 fix(agent): clear auth_token when authenticating via api_key (#105774) · duplicate → #105778, #105774

Closed issues · 1

Closed#105774`ANTHROPIC_AUTH_TOKEN` from the environment is sent to third-party Anthropic-compatible endpoints (dual-auth credential leak)

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs: #107978
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 11 Sep 2026

For your agent

The same facts, typed.

cluster/105774.json
cluster/105774.md