Cairn
NousResearch/hermes-agent

Guard sensitive config keys from CLI mutation

Cluster 81101 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 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
1 issue and 1 PR.

These items address a missing security gate in the Hermes CLI that allows sensitive security-policy keys (such as approvals.mode) to be modified via config set/unset without restriction. The work involves adding guards to prevent unauthorized or unintended mutation of those keys.

Open issues1

  • Issue#81101`config set`: no sensitive-key guard — agent can flip `approvals.mode` (the security policy) via the official CLI with no gate

Open PRs1

  • PR#104697fix(config): guard security-policy keys in hermes config set/unset (salvage of #81108)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #81108 fix(config): guard security-policy keys in hermes config set/unset · superseded by another PR → #104697, #59293
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.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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/81101.json
cluster/81101.md