Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix Can users customize prompts in agent/prompt_builder.py? [1 pull requests, 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#19752•Fetched 2026-05-05 06:05:22
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
calicoagentcalicoagent
Participants
calicoagentcalicoagent
Timeline (top)
labeled ×4cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #19987: docs(prompt): clarify supported customization surfaces

Description (problem / solution / changelog)

Summary

  • document the supported prompt customization surfaces instead of leaving prompt_builder.py as an implied user-editable seam
  • clarify when users should edit SOUL.md, project context files, skills, or ephemeral overlays
  • explicitly frame agent/prompt_builder.py as implementation code unless the operator is maintaining a fork

Closes #19752

Changed files

  • website/docs/developer-guide/prompt-assembly.md (modified, +24/-0)
RAW_BUFFERClick to expand / collapse

Question

Looking at agent/prompt_builder.py and agent/prompt_caching.py, can users customize the prompts defined/assembled there directly, or is all user-level customization expected to flow through the Markdown layer (SOUL.md, MEMORY.md, USER.md, skills)?

What I'm trying to clarify

  • Are there string templates / system prompt fragments inside prompt_builder.py that are intended to be user-editable?
  • If a user wants to fully override the assembled system prompt, what is the supported path?
  • Any docs pointer beyond website/docs/developer-guide/prompt-assembly.md?

Thanks.

extent analysis

TL;DR

Users should flow their customization through the Markdown layer for supported customization of system prompts.

Guidance

  • Review the website/docs/developer-guide/prompt-assembly.md documentation for the recommended approach to customizing system prompts.
  • Check agent/prompt_builder.py and agent/prompt_caching.py for any explicit comments or docstrings indicating user-editable sections or override mechanisms.
  • If intending to override the assembled system prompt, look for guidance on using the Markdown layer (SOUL.md, MEMORY.md, USER.md, skills) as the primary customization path.

Notes

The issue lacks explicit information on direct customization of prompt_builder.py and prompt_caching.py, so caution is advised when modifying these files directly.

Recommendation

Apply workaround: Use the Markdown layer for customization, as it is the supported path, to avoid potential issues with direct modifications to the Python files.

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