hermes - ✅(Solved) Fix Redundant .hermes directory when running /plan inside hermes-agent repo [1 pull requests, 1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#12894Fetched 2026-04-20 12:16:19
View on GitHub
Comments
1
Participants
1
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
commented ×1

PR fix notes

PR #12895: fix: anchor /plan storage to get_hermes_home() to avoid redundant .hermes dirs

Description (problem / solution / changelog)

This PR anchors the plan storage path to the global Hermes home directory instead of using a relative path. This prevents the creation of redundant .hermes directories within project workspaces that are already managed by Hermes.

Changes:

  • Modified agent/skill_commands.py to use get_hermes_home() in build_plan_path.
  • Updated skills/software-development/plan/SKILL.md to reflect the change to absolute home paths and explain the benefit (preventing workspace pollution).

Verification:

  • Verified that /plan now saves to ~/.hermes/plans/ even when the CWD contains a .hermes folder.
  • Verified that skill_commands.py passes syntax checks.

Changed files

  • agent/skill_commands.py (modified, +2/-2)
  • skills/software-development/plan/SKILL.md (modified, +6/-6)
RAW_BUFFERClick to expand / collapse

When running the /plan command inside the hermes-agent repository (or any project that already contains a .hermes directory), the generated plan is stored at .hermes/plans/. This results in a nested path like /path/to/hermes-agent/.hermes/plans/, which is redundant and inconsistent with the global home directory preference (~/.hermes/).

The build_plan_path function in agent/skill_commands.py currently hardcodes Path(".hermes"), which is relative to the current working directory. It should instead use get_hermes_home() to anchor the plans to the user's persistent Hermes directory.

extent analysis

TL;DR

The issue can be fixed by modifying the build_plan_path function to use get_hermes_home() instead of hardcoding the relative path.

Guidance

  • Identify the build_plan_path function in agent/skill_commands.py and locate the hardcoded Path(".hermes").
  • Replace the hardcoded path with a call to get_hermes_home() to anchor the plans to the user's persistent Hermes directory.
  • Verify the change by running the /plan command and checking the generated plan's storage location.
  • Consider adding a test to ensure the plan path is correctly resolved in different working directories.

Example

# Before
plan_path = Path(".hermes") / "plans"

# After
from hermes.utils import get_hermes_home
plan_path = get_hermes_home() / "plans"

Notes

This fix assumes that get_hermes_home() correctly returns the user's persistent Hermes directory. If this function is not properly implemented, additional changes may be necessary.

Recommendation

Apply the workaround by modifying the build_plan_path function to use get_hermes_home(), as this should resolve the issue and provide a consistent plan storage location.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - ✅(Solved) Fix Redundant .hermes directory when running /plan inside hermes-agent repo [1 pull requests, 1 comments, 1 participants]