Cairn
NousResearch/hermes-agent

Allow agent writes to its own ~/.hermes/.env file

Cluster 47107 · agent. 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 members address a restriction in write_file/patch that blocks the agent from writing to its own active profile .env file at ~/.hermes/.env. The group covers the problem report and related fix attempts.

Open issues1

  • Issue#47107write_file/patch blocks agent from writing to its own ~/.hermes/.env

Open PRs1

  • PR#47114fix(agent): allow write_file/patch to modify active profile .env

1 PR closed without merging

From the close comments: other 1

  • #47141 fix(file-safety): allow agent to write to its own ~/.hermes/.env (#47107) · other
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/47107.json
cluster/47107.md