NousResearch/hermes-agent

Redact secrets in interrupt_debug.log output

Cluster 75461 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

A bug was identified where secrets bypass the RedactingFormatter and are written unredacted to interrupt_debug.log. These members address passing interrupt_debug.log messages through redact_sensitive_text to fix this.

Open issues1

  • Issue#75461Secrets written unredacted to interrupt_debug.log (bypasses RedactingFormatter)

Open PRs0

No open pull requests.

3 PRs closed without merging

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

  • #75476 fix(redact): pass interrupt_debug.log messages through redact_sensitive_text (#75461) · stale or abandoned
  • #76043 fix(cli): redact secrets in interrupt_debug.log writes (#75461) · duplicate → #75476, #75461
  • #76260 fix(cli): redact secrets in interrupt_debug.log writes (#75461) · duplicate → #75476
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
hermes cli
Closed issues
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.