Cairn

Skill file write controls and read-only enforcement

NousResearch/hermes-agent · cluster 32497 · agent

Data as of

3 open items. Fix merged in #98254. Check it covers your case.

The short answer

2open issues
1open PR
7items grouped
Known?
Yes. 7 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #98254. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 1 PR.

These items concern unintended or ungated modifications to skill files during normal agent operation, and efforts to add read-only enforcement, review gates, and proper toolset restrictions around skill writes. One feature request item does not clearly share this theme.

Open issues2

  • Issue#32497[Bug]: Hermes unexpectedly modifies its own skills/system prompts during normal task execution, even when the user request is unrelated to agent configuration.
  • Issue#45576skill_manage tool: skill files written without corresponding tool call record

Open PRs1

  • PR#64996fix(skills): add skills.read_only hard deny for runtime skill writes

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #98254 Background review lands skill patches again — read tools whitelisted, cache parity intact (#61521, #39996)

    merged to main

    files: agent/background_review.py, tests/run_agent/test_background_review_toolset_restriction.py, tools/file_tools.py

1 PR closed without merging

From the close comments: done elsewhere 1

  • #64964 fix(background-review): gate skills toolset on review_skills flag · done elsewhere → #98254
Closed issues · 2
  • Closed#51171[Feature]: If Hermes agent doesn't release the skill control module soon, I'll have to switch back to OpenClaw.
  • Closed#64926[Bug]: Skill files are modified automatically during normal conversation and cannot be made read-only by config
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.19: 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
Merged PRs
#98254
Closed issues
2
Attempts
1 PR closed without merging
Fix link checked
30 Aug 2026

For your agent

The same facts, typed.

cluster/32497.json
cluster/32497.md