Skip to content

fix(paths): respect HERMES_HOME for protected Hermes env path - #3232

Closed
erhnysr wants to merge 1 commit into
NousResearch:mainfrom
erhnysr:fix/hermes-home-followup
Closed

fix(paths): respect HERMES_HOME for protected Hermes env path#3232
erhnysr wants to merge 1 commit into
NousResearch:mainfrom
erhnysr:fix/hermes-home-followup

Conversation

@erhnysr

@erhnysr erhnysr commented Mar 26, 2026

Copy link
Copy Markdown
Contributor

Summary

Updates the protected write deny list to respect HERMES_HOME instead of using a hardcoded ~/.hermes/.env path.

Why

The deny list should follow the active Hermes profile. Hardcoding ~/.hermes/.env bypasses HERMES_HOME and can miss the actual protected env file in custom or multi-instance setups.

Changes

  • Replaced the hardcoded Hermes env path in tools/file_operations.py
  • Uses get_hermes_home() for consistency with the rest of the codebase

Scope

Minimal path-consistency fix with no behavior change beyond correctly respecting HERMES_HOME.

@erhnysr

erhnysr commented Mar 26, 2026

Copy link
Copy Markdown
Contributor Author

The failing test may be expecting the hardcoded ~/.hermes/.env path.

This PR updates the path resolution to respect HERMES_HOME via get_hermes_home(), which changes the exact string but preserves the intended behavior.

Happy to update tests if needed.

@erhnysr

erhnysr commented Mar 26, 2026

Copy link
Copy Markdown
Contributor Author

Added the legacy ~/.hermes/.env deny path back alongside the HERMES_HOME-resolved path to preserve compatibility while still respecting custom Hermes home directories.

teknium1 pushed a commit that referenced this pull request Mar 30, 2026
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 added a commit that referenced this pull request Mar 30, 2026
…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 #3232 by @erhnysr.

Co-authored-by: Erhnysr <erhnysr@users.noreply.github.com>
@teknium1

Copy link
Copy Markdown
Contributor

Merged via #3840 with authorship preserved. Thanks @erhnysr!

@teknium1 teknium1 closed this Mar 30, 2026
angelburgosrosado pushed a commit to angelburgosrosado/hermes-agent that referenced this pull request Apr 27, 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>
02356abc pushed a commit to 02356abc/hermes-agent that referenced this pull request May 14, 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>
gweeteve pushed a commit to gweeteve/hermes-agent that referenced this pull request Jun 2, 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>
waefrebeorn pushed a commit to waefrebeorn/slermes that referenced this pull request Jul 2, 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>
Sarthib7 added a commit to Sarthib7/hermes-agent that referenced this pull request Jul 14, 2026
The live Task.status enum gained QUEUED (accepted by a coworker,
waiting to start; sokosumi PR NousResearch#3232, 2026-06-22) and APPROVAL_REQUIRED
(blocked on human approval; sokosumi PR NousResearch#3180, 2026-06-15) — verified
against https://api.sokosumi.com/v1/openapi.json on 2026-07-14.

Add APPROVAL_REQUIRED to the helper's TASK_BLOCKED set so 'wait task'
exits 2 (blocked) instead of polling to timeout, update the SKILL.md
status table to the 14-value task enum, and reword the QUEUED pitfall
(it is a task-only status; still never a job or job-event status).
Two new tests; 39 total.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants