Discord slash command detection bug and fixes
Cluster 5865 · gateway. Data as of
1 open item. Fix merged in #13187 on 20 Apr 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- A fix was merged to main in PR #13187. 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
- 1 issue and 0 PRs.
Next step: read #13187, then check whether your report is the one still open.
Read #13187Pick up a Lab taskA bug was identified where Discord slash commands were not properly recognized, particularly when auto-create-thread is enabled. Related fixes were gathered and applied to address this detection issue.
Open issues1
- Issue#5865[Bug]: Discord /slash commands not being properly recognized when in channel
Open PRs0
Fixes on record
-
#13187 fix: salvage tier-1 bug fixes from PRs #7387, #9091, #6293, #13131
files:
cli.py,gateway/platforms/discord.py,gateway/platforms/telegram.py,hermes_cli/setup.py,scripts/release.py,tests/e2e/conftest.py,tests/e2e/test_discord_adapter.py,tests/hermes_cli/test_setup_openclaw_migration.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#6293 fix(discord): fix slash command detection when auto-create-thread is on · merged via another change →
#13187
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.00means 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 LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #13187
- Closed issues
- 0
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.