Cairn
NousResearch/hermes-agent

Profile secret scoping for Anthropic token resolution and related credential reads

Cluster 51603 · agent. Data as of

Nothing open on GitHub. Fix merged in #76462 on 1 Aug 2026. Check it covers your case.

The short answer

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

The members share one theme: resolve_anthropic_token() reportedly bypasses profile secret scope, with a bug report describing possible cross-profile credential exposure in multiplex mode. Related items cover scope isolation for cron credential reads and wider secret-scope migration (get_env_value, anthropic adapter, ACP env scrub); titles alone do not show their status.

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.

  • #76462 fix(secrets): finish profile secret-scope migration — get_env_value, anthropic adapter, ACP env scrub (cluster salvage)

    merged to main

    files: agent/anthropic_adapter.py, contributors/emails/[redacted:email], hermes_cli/config.py, hermes_cli/env_loader.py, tests/agent/test_anthropic_token_scope_isolation.py, tests/hermes_cli/test_env_loader.py, tests/hermes_cli/test_get_env_value_scope.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #51604 fix(auth): scope-isolate resolve_anthropic_token() and cron credential reads · merged via another change → 18e0683, fdab380, #76462, #51603
  • #68797 fix(auth): resolve_anthropic_token() bypasses profile secret scope · done elsewhere → 18e0683, #76462, #51604
Closed issues · 1
  • Closed#51603bug(auth): resolve_anthropic_token() bypasses profile secret scope — cross-profile credential leak in multiplex mode
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

Subsystem
agent
Merged PRs
#76462
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
1 Aug 2026

For your agent

The same facts, typed.

cluster/51603.json
cluster/51603.md