Cairn

SimpleX adapter DM routing and silent drop bugs

NousResearch/hermes-agent · cluster 44400 · gateway

Data as of

Nothing open on GitHub. Fix merged in #81588. Check it covers your case.

The short answer

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

Multiple bug reports and fixes addressing the SimpleX adapter silently dropping direct messages due to incorrect contact addressing, where numeric contactId values were being treated as display names. Related fixes apply structured send commands and correct inbound message handling.

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.

  • #81588 fix(simplex): use structured /_send for all DM text sends

    merged to main

    files: plugins/platforms/simplex/adapter.py, tests/gateway/test_simplex_plugin.py

3 PRs closed without merging

From the close comments: merged via another change 2 · duplicate 1

  • #44444 fix(simplex): use structured /_send for DM text messages to prevent silent drops · merged via another change → #81588
  • #46328 fix(simplex): use structured /_send for DMs to fix silent message drops · duplicate → #44444
  • #46377 fix(simplex): use structured /_send for standalone DM text sends · merged via another change → #81588
Closed issues · 3
  • Closed#44400Simple X Adapter: Bug Report from my Agent: SimpleX Chat
  • Closed#46265[Bug]: SimpleX adapter silently drops all DM replies — `@<contactId>` syntax resolves as display name, not contactId
  • Closed#63109SimpleX adapter: DM text send addresses a numeric contactId as a display name → chatCmdError, silently dropped
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.29: 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
Merged PRs
#81588
Closed issues
3
Attempts
3 PRs closed without merging
Fix link checked
8 Aug 2026

For your agent

The same facts, typed.

cluster/44400.json
cluster/44400.md