Cairn
NousResearch/hermes-agent

Guard config.yaml mutations from execute_code tool

Cluster 113421 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These issues and PRs address a bug where execute_code could silently mutate the protected config.yaml, bypassing the write guard enforced by other tools like write_file and patch. The work focuses on detecting and loudly failing on such runtime config mutations.

Open issues0

No open issues.

Open PRs3

  • PR#113450fix(tools): fail loudly when execute_code rewrites the protected config
  • PR#113458fix(approval): detect runtime config mutations safely
  • PR#113459fix(tools): execute_code fails loudly when the cell mutates config.yaml (#113421)
Closed issues · 1
  • Closed#113421[Bug]: execute_code bypasses the config.yaml write guard that write_file/patch enforce
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
agent
Closed issues
1
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/113421.json
cluster/113421.md