NousResearch/hermes-agent

Block sync_back writes into protected host directories

Cluster 38026 · environments. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue 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
Nothing open on GitHub.

These changes add safeguards to prevent sync_back operations from writing into host skill, config, or Hermes state directories. The fixes appear across both tools and remote-backend components.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: partial fix 1 · won't fix / by design 1 · other 1

  • #38027 fix(remote-backend): prevent sync_back writes into host skill dirs · partial fix → 047e7cf, 1148502, #38026
  • #38715 fix(tools): block sync_back writes into host skill/config dirs (#38026) · other
  • #56825 fix(tools): block sync_back writes into Hermes state · won't fix / by design → #38026, #38715
Closed issues · 1
  • Closed#38026fix(remote-backend): prevent sync_back writes into host skill dirs
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
environments
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.