Skip to content

fix(paths): respect HERMES_HOME for protected .env write-deny path#3840

Merged
teknium1 merged 1 commit intomainfrom
hermes/hermes-b2abefdf
Mar 30, 2026
Merged

fix(paths): respect HERMES_HOME for protected .env write-deny path#3840
teknium1 merged 1 commit intomainfrom
hermes/hermes-b2abefdf

Conversation

@teknium1
Copy link
Copy Markdown
Contributor

The write-deny list in file_operations.py hardcoded ~/.hermes/.env, which misses the actual .env in custom HERMES_HOME or profile setups. Uses get_hermes_home() for profile-safe path resolution.

Salvaged from PR #3232 by @erhnysr with authorship preserved.

Note: PR #3205 (same author, file_tools.py) was already fixed on main via commit e97c0cb.

The write-deny list in file_operations.py hardcoded ~/.hermes/.env,
which misses the actual .env in custom HERMES_HOME or profile setups.
Use get_hermes_home() for profile-safe path resolution.

Salvaged from PR #3232 by @erhnysr.
@teknium1 teknium1 merged commit 59f2b22 into main Mar 30, 2026
2 checks passed
itsXactlY pushed a commit to itsXactlY/hermes-agent that referenced this pull request Mar 30, 2026
…ousResearch#3840)

The write-deny list in file_operations.py hardcoded ~/.hermes/.env,
which misses the actual .env in custom HERMES_HOME or profile setups.
Use get_hermes_home() for profile-safe path resolution.

Salvaged from PR NousResearch#3232 by @erhnysr.

Co-authored-by: Erhnysr <erhnysr@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants