# NousResearch/hermes-agent · Discord slash command detection bug and fixes

## Open now

- 1 issue, 0 PRs open on GitHub.
- #5865: \[Bug\]: Discord /slash commands not being properly recognized when in channel

A 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.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #13187. Verify it addresses your case.
- **Recommended:** read PR #13187 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

- #5865: \[Bug\]: Discord /slash commands not being properly recognized when in channel

## Prior & competing PRs

- **#13187: fix: salvage tier-1 bug fixes from PRs #7387, #9091, #6293, #13131**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - 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`
- **#6293: fix(discord): fix slash command detection when auto-create-thread is on**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#13187`

## Fix status

- Merged to main in PR #13187 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-20`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.
- Subsystem: `gateway`