NousResearch/hermes-agent

Gateway delivery target ID parsing and related Slack fixes

Cluster 11768. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #18553 on 1 May 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #18553. 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.

Next step: read #18553, then check it covers your case.

Read #18553 Pick up a Lab task

Two members concern explicit delivery target IDs in the gateway, with one reporting that DeliveryTarget.parse corrupts explicit chat IDs and Matrix room targets and the other titled as a fix for preserving them. A third member is a broader Slack batch covering reserved commands, session isolation, and delivery fixes, so it only partly overlaps the others.

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.

#18553 fix(gateway/slack): batch salvage — reserved commands, session isolation, delivery fixes

merged to main

files: gateway/delivery.py, gateway/platforms/discord.py, gateway/platforms/slack.py, hermes_cli/commands.py, scripts/release.py, tests/gateway/test_delivery.py, tests/gateway/test_discord_free_response.py, tests/gateway/test_slack.py, tests/gateway/test_slack_mention.py, tests/hermes_cli/test_commands.py

1 PR closed without merging

From the close comments: superseded by another PR 1

#11962 fix(gateway): preserve explicit delivery target ids · superseded by another PR → #11893, #11768

Closed issues · 1

Closed#11768bug(gateway): DeliveryTarget.parse corrupts explicit chat IDs and Matrix room targets

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

Merged PRs: #18553
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 1 May 2026

For your agent

The same facts, typed.

cluster/11768.json
cluster/11768.md