Cairn
NousResearch/hermes-agent

Secret redaction gap in file tool outputs

Cluster 363 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

These items concern a security issue where sensitive credentials visible in file tool outputs (e.g., read_file) are not redacted, unlike terminal outputs. The work involves applying consistent automatic secret redaction across tool output types.

Open issues0

No open issues.

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: other 1

  • #372 fix: apply secret redaction to file tool outputs · other
Closed issues · 2
  • Closed#363Security: File Tool Output Redaction Gap — Secrets Exposed via read_file but Masked via Terminal
  • Closed#18595Security: Auto-redact sensitive credentials from tool outputs (read_file, terminal, etc.)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: 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
Closed issues
2
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/363.json
cluster/363.md