Restrict writes to sensitive paths under HERMES_HOME
Cluster 110464 · agent. Data as of
1 open item. Fix merged in #111409 on 15 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #111409. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111409. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items address gaps where write and patch operations could overwrite sensitive credential stores, secret files, and browser profile data under HERMES_HOME. The work involves aligning write denylists with read denylists and adding specific protections for vault, OAuth, and password manager cache paths.
Open issues0
Open PRs1
- PR#110465fix(security): write-deny HERMES_HOME secret stores
Fixes on record
-
#111409 fix(file-safety): write_file/patch no longer overwrite vault, browser-profile, Google OAuth and Bitwarden cache under HERMES_HOME (#110464, salvage #110465)
files:
agent/file_safety.py,tests/agent/test_file_safety_write_credentials.py,website/docs/user-guide/security.md
Closed issues · 1
- Closed#110464write denylist drifted from the read credential denylist
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
- #111409
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 15 Sep 2026