Cairn
NousResearch/hermes-agent

Gateway sessions not applying SOUL.md or personality identity

Cluster 6731 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 4 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Most members concern gateway sessions (Telegram, Feishu) that appear to use the default agent identity instead of custom SOUL.md/AGENTS.md or personality settings, including wiring of the load_soul_identity config. One member addresses a related but distinct topic: evicting cached agents across fresh session boundaries.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: closed without comment 1 · done elsewhere 1 · other 1

  • #6761 fix(gateway): evict cached agents across fresh session boundaries · closed without comment
  • #26789 fix(gateway): honor SOUL.md and agent.personality in gateway sessions · other → #26596
  • #37520 fix(gateway): wire agent.load_soul_identity config to gateway AIAgent construction (#37480) · done elsewhere
Closed issues · 4
  • Closed#6731Feishu bot uses hardcoded DEFAULT_AGENT_IDENTITY instead of SOUL.md for system prompt
  • Closed#26596[Bug] Gateway mode ignores SOUL.md and agent.personalities — DEFAULT_AGENT_IDENTITY always used
  • Closed#32843[Bug]: SOUL.md and AGENTS.md not loaded for Telegram gateway sessions in v0.14.0
  • Closed#37480Gateway (Telegram) ignores custom SOUL.md + AGENTS.md — serves DEFAULT_AGENT_IDENTITY despite correct paths, default profile, and load_soul_identity=true
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.21: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
4
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/6731.json
cluster/6731.md