Cairn

Cross-channel mirror session gaps and silent failures

NousResearch/hermes-agent · cluster 10130 · agent

Data as of

4 open items. Fix merged in #109129. Check it covers your case.

The short answer

2open issues
2open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #109129. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #109129. That is separate from the fix event.
Still open
2 issues and 2 PRs.

These items address cases where cross-channel message mirroring silently skips or fails without surfacing errors to callers, operators, or logs. Concerns span missing mirror sessions, undetected transcript write failures, and resulting context loss when recipients reply.

Open issues2

  • Issue#33530send_message cross-channel amnesia: agent has no context of outbound messages when recipient replies
  • Issue#54273Observability gap: tools/send_message silently drops mirror-to-session, leaving operators and tool callers blind

Open PRs2

  • PR#33690fix(gateway): create mirror sessions for cross-channel targets when none exist (#33530)
  • PR#54272tools/send_message: surface silent mirror-skip to caller + warn-log

Fixes on record

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

  • #109129 mirror_to_session no longer reports success when the transcript write fails (#10130)

    merged to main

    files: gateway/mirror.py, tests/gateway/test_mirror.py

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #10323 fix(mirror): report transcript write failures · superseded by another PR → eca2cea, #109129, #10130
  • #99207 fix(send_message): record outbound message in source session when target channel session not found · other → #33530
Closed issues · 1
  • Closed#10130gateway mirror_to_session returns success even when both transcript writes fail
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.20: 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
Merged PRs
#109129
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
12 Sep 2026

For your agent

The same facts, typed.

cluster/10130.json
cluster/10130.md