Cairn

Memory and cron context trust boundary fixes

NousResearch/hermes-agent · cluster 26714 · agent

Data as of

8 open items. Fix attempted, not merged.

The short answer

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

These issues and fixes address cases where unconfirmed or stale context—from memory, cron outputs, or quoted replies—is treated as authoritative, potentially corrupting routing decisions or persisting policy claims without explicit approval. The work spans reducing trust in background context and adding explicit staging or redaction before such inputs affect live sessions.

Open issues4

  • Issue#26714Telegram replies to cron deliveries can revive stale tasks via quoted cron context
  • Issue#44963Make memory Write Gate approvals explicit and staged
  • Issue#63469[Bug]: orchestrator trusts stale memory over canonical policy and corrupts multi-profile model routing
  • Issue#64681[Bug]: quoted/ambiguous text can become a permanent model ban without confirmation

Open PRs4

  • PR#26725fix(gateway): redact cron reply context in live turns
  • PR#63544fix(memory): demote memory context from authoritative to informational background (#63469)
  • PR#72988fix(memory): stage unconfirmed policy claims instead of silently persisting
  • PR#104611Improve memory Write Gate review flow — re-land on current main
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.18: 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
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/26714.json
cluster/26714.md