Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Feature]: Provide a convenient way of making Hermes aware of PATHs [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#17799•Fetched 2026-05-01 05:55:42
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
sebthirietsebthiriet
Participants
sebthirietsebthiriet
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

Problem or Use Case

Hermes is not aware of PATHs we have setup in the interactif shell. Hermes standard profile seems to load ~/.profile but subprofiles do not load this file. It results in inconsistencies wether a script is ran by the main profile or subprofiles.

Proposed Solution

In my opinion, would be helpful to be able to declare additional PATHs in the config.yaml. Or just making official the fact that each agent will load .profile or .bashrc at the beginning of each session initiated in CLI or through the cron

Alternatives Considered

No response

Feature Type

New tool

Scope

None

Contribution

  • I'd like to implement this myself and submit a PR

Debug Report (optional)

extent analysis

TL;DR

Declare additional PATHs in the config.yaml or ensure subprofiles load ~/.profile or ~/.bashrc to resolve inconsistencies.

Guidance

  • Verify that the main profile loads ~/.profile correctly and identify why subprofiles do not.
  • Consider adding a feature to load ~/.profile or ~/.bashrc for subprofiles to maintain consistency.
  • Explore declaring additional PATHs in the config.yaml as a potential workaround.
  • Test scripts run by both the main profile and subprofiles to identify specific inconsistencies.

Example

No code snippet is provided as the issue does not contain sufficient technical details.

Notes

The solution may require modifications to Hermes' configuration or codebase, and the feasibility of declaring additional PATHs in config.yaml is uncertain without further information.

Recommendation

Apply workaround: Declare additional PATHs in the config.yaml or ensure subprofiles load ~/.profile or ~/.bashrc, as this approach may provide a quicker resolution to the inconsistencies.

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…
#autograd error#model save/load#optimization#mixed precision#training loop

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 - 💡(How to fix) Fix [Feature]: Provide a convenient way of making Hermes aware of PATHs [1 participants]