Bug Description
When a hermes_local agent runs a heartbeat, the content of AGENTS.md (and other instruction files like HEARTBEAT.md, SOUL.md, TOOLS.md) is not injected into the hermes prompt context. The agent only receives the Paperclip-generated heartbeat prompt.
Steps to Reproduce
- Configure a hermes_local agent with custom instructions in AGENTS.md
- Trigger a heartbeat run
- Inspect the session JSON at ~/.hermes/sessions/session_.json
- Check messages[0].content for AGENTS.md content
Expected
The agent's AGENTS.md instructions should appear in the injected context, as they do for claude_local agents.
Actual
Only the Paperclip-generated heartbeat prompt is present. Custom instructions (delegation rules, memory guidance, skill-saving rules) never reach the agent.
Impact
Any hermes_local agent configuration done via the Instructions tab (AGENTS.md, HEARTBEAT.md, SOUL.md) is silently ignored. Agents cannot be customized beyond what the hardcoded heartbeat prompt provides.
Related
Environment
- Paperclip: v2026.416.0-canary.1
- Hermes Agent: v0.8.0
- hermes-paperclip-adapter: (bundled with paperclipai)
Bug Description
When a hermes_local agent runs a heartbeat, the content of AGENTS.md (and other instruction files like HEARTBEAT.md, SOUL.md, TOOLS.md) is not injected into the hermes prompt context. The agent only receives the Paperclip-generated heartbeat prompt.
Steps to Reproduce
Expected
The agent's AGENTS.md instructions should appear in the injected context, as they do for claude_local agents.
Actual
Only the Paperclip-generated heartbeat prompt is present. Custom instructions (delegation rules, memory guidance, skill-saving rules) never reach the agent.
Impact
Any hermes_local agent configuration done via the Instructions tab (AGENTS.md, HEARTBEAT.md, SOUL.md) is silently ignored. Agents cannot be customized beyond what the hardcoded heartbeat prompt provides.
Related
Environment