Cairn
NousResearch/hermes-agent

Cron delivery channel routing and name resolution

Cluster 2943 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs concern bugs where cron-triggered deliveries route to incorrect channels and where channel names are not converted to IDs before delivery, specifically affecting Discord and Slack integrations.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: closed without comment 1 · done elsewhere 1 · other 1

  • #2946 fix(cron): resolve channel names to IDs before Discord delivery · closed without comment
  • #2947 fix(cron): resolve channel names to IDs before Discord delivery · done elsewhere → #3860
  • #2948 fix(cron): resolve Discord/Slack channel names to IDs before delivery · other → 3fad1e7, #3860
Closed issues · 1
  • Closed#2943[Bug]: Discord API error in gateway
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.50: 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
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/2943.json
cluster/2943.md