Cairn
NousResearch/hermes-agent

Gateway pairing list read on every message

Cluster 77440 · gateway. Data as of

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

The short answer

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

A bug and two related performance improvements addressing repeated disk reads and parsing of the pairing approved list on each inbound gateway message. The work involves caching and moving file I/O off the event loop.

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.

  • #120405 perf(gateway): take file I/O and per-message scans off the event loop

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], gateway/pairing.py, gateway/platforms/api_server.py, gateway/platforms/base.py, gateway/platforms/weixin.py, gateway/run_turn.py, plugins/platforms/buzz/adapter.py, plugins/platforms/slack/adapter.py, plugins/platforms/telegram/adapter.py, tests/gateway/test_api_server_artifact_store_async.py, tests/gateway/test_buzz_adapter.py, tests/gateway/test_pairing.py, tests/gateway/test_proxy_mode.py, tests/gateway/test_slack_unfurl_nested_blocks_budget.py, tests/gateway/test_weixin.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #77441 perf(gateway): cache pairing approved list by file mtime instead of re-reading per message · merged via another change → #120405
Closed issues · 1
  • Closed#77440[Bug]: pairing approved list is re-read from disk and re-parsed on every inbound gateway message
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

Subsystem
gateway
Merged PRs
#120405
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
23 Sep 2026

For your agent

The same facts, typed.

cluster/77440.json
cluster/77440.md