NousResearch/hermes-agent
Overly broad secret redaction regex false positives
Cluster 10983 · agent. Data as of
Nothing open on GitHub. Fix merged in #109110 on 12 Sep 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #109110. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #109110. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address cases where the secret/key redaction logic incorrectly matches ordinary identifiers, filenames, and snake_case paths (particularly those starting with sk_ or am_) due to overly broad regex patterns.
Open issues0
Open PRs0
Fixes on record
-
#109110 fix(redact): ordinary am_* identifiers are no longer masked in tool output (#10983, salvage #11124)
files:
agent/redact.py,tests/agent/test_redact.py
1 PR closed without merging
From the close comments: other 1
- #11010 Avoid redacting plain AgentMail-like identifiers · other
Closed issues · 1
- Closed#10983[Bug]: Redaction incorrectly masks ordinary am_* identifiers
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.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #109110
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 12 Sep 2026