NousResearch/hermes-agent

Persist internal-event prompt pins across gateway restart

Cluster 125793. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #126137 on 28 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #126137. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #126137. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #126137, then check it covers your case.

Read #126137 Pick up a Lab task

A bug was identified where internal-event prompt pins were stored only in memory, causing the system prompt to flip unexpectedly after a gateway restart. Two fix attempts address persisting these pins so they survive restarts.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#126137 fix(gateway): persist internal prompt pins across restart (salvage #125832)

merged to main

files: gateway/run_agent_cache.py, gateway/run_startup.py, gateway/run_turn.py, gateway/session.py, gateway/session_persistence.py, gateway/session_prompt_pin.py, gateway/session_state.py, gateway/slash_commands_session.py, tests/gateway/test_handoff_secondary_profile_adapter.py, tests/gateway/test_internal_event_pin_wiring.py, tests/gateway/test_resume_command.py, tests/gateway/test_session.py, tests/gateway/test_telegram_topic_mode.py

1 PR closed without merging

From the close comments: stale or abandoned 1

#125832 fix(gateway): persist internal prompt pins across restart · stale or abandoned → 8928355, bac0c45, 801a902, #125793, #125783, #125784

Closed issues · 1

Closed#125793[Bug]: Internal-event pins are in-memory: the first internal event after a gateway restart still flips the system prompt

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: 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

Merged PRs: #126137
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 28 Sep 2026

For your agent

The same facts, typed.

cluster/125793.json
cluster/125793.md