Cairn

Gating agent edits to skills behind user approval

NousResearch/hermes-agent · cluster 17583 · skills

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

These issues and PRs explore mechanisms to prevent agents from autonomously modifying or creating skills without explicit user confirmation, including locked tiers, protected dotfiles, and confirmation gates for skill mutations.

Open issues2

  • Issue#25083Feature: Immutable/protected skills - prevent agent from modifying critical skills without user approval
  • Issue#41939feat(skills): deterministic opt-in protection for personal skills against agent edits

Open PRs2

  • PR#26560fix(skills): block agent mutations of immutable skills
  • PR#42223feat(skills): add deterministic opt-in protection for personal skills

2 PRs closed without merging

From the close comments: closed without comment 1 · other 1

  • #17609 feat(skills): add user-lock and approval gate for skill mutations · other
  • #26547 fix(skills): gate background review writes behind approval · closed without comment
Closed issues · 3
  • Closed#17583Skills: user-locked vs self-improving tiers + user-feedback-driven skill updates
  • Closed#21315[Feature]: Add `skills.evolution_mode` — confirmation gate for autonomous skill evolution
  • Closed#26298[Feature]: skill creation should ask user for confirmation — especially when a同名 skill already exists
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.15: 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
skills
Closed issues
3
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/17583.json
cluster/17583.md