NousResearch/hermes-agent

Slack response_url error handling and body read limits

Cluster 55356 · gateway. Data as of 2026-10-28 11:56 UTC

Nothing open on GitHub. Fix merged in #69479 on 23 Jul 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 #69479. 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 #69479, then check it covers your case.

Read #69479 Pick up a Lab task

These items address unbounded response body reads and hardening of slash/bang command handling in Slack response_url delivery. The work involves bounding error body reads and improving parse order and session key 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.

#69479 fix(slack): harden slash/bang command handling — parse order, session keys, response_url delivery

merged to main

files: contributors/emails/[email protected], contributors/emails/[redacted:email], contributors/emails/[redacted:email], gateway/platforms/base.py, gateway/run.py, plugins/platforms/slack/adapter.py, tests/e2e/test_platform_commands.py, tests/gateway/test_queue_command.py, tests/gateway/test_slack.py, tests/gateway/test_slack_approval_buttons.py, tests/gateway/test_slack_send_retry.py, tests/gateway/test_steer_command.py

1 PR closed without merging

From the close comments: merged via another change 1

#55357 fix(slack): bound response_url error body reads · merged via another change → #69479, #55356

Closed issues · 1

Closed#55356Slack response_url failures read oversized response bodies unbounded

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: #69479
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 23 Jul 2026

For your agent

The same facts, typed.

cluster/55356.json
cluster/55356.md