Skip to content

fix(discord): clean up deferred "thinking..." after slash commands complete#3674

Merged
teknium1 merged 1 commit intomainfrom
hermes/hermes-b8464e26
Mar 29, 2026
Merged

fix(discord): clean up deferred "thinking..." after slash commands complete#3674
teknium1 merged 1 commit intomainfrom
hermes/hermes-b8464e26

Conversation

@teknium1
Copy link
Copy Markdown
Contributor

Summary

Fixes #3595. The Discord "thinking..." deferred response indicator persisted after slash commands completed because the code used followup.send() — which creates a separate ephemeral message — instead of editing or deleting the deferred response.

Fix

In _run_simple_slash():

  • With confirmation text (e.g. /new → "New conversation started~"): use edit_original_response() to replace "thinking..." with the confirmation
  • Without confirmation (e.g. /usage, /help): use delete_original_response() to remove the "thinking..." indicator

Also consolidated /reasoning and /voice handlers to use _run_simple_slash instead of duplicating the defer+dispatch pattern (they had the same bug — no cleanup after defer).

Test plan

  • 70 Discord tests + 17 slash command tests all pass
  • Needs live verification on a Discord server to confirm the "thinking..." clears
…mplete

After a slash command is deferred (interaction.response.defer), the
"thinking..." indicator persisted indefinitely because the code used
followup.send() which creates a separate message instead of replacing
or removing the deferred response.

Fix: use edit_original_response() to replace "thinking..." with the
confirmation text when provided, or delete_original_response() to
remove it when there is no confirmation. Also consolidated /reasoning
and /voice handlers to use _run_simple_slash instead of duplicating
the defer+dispatch pattern.

Fixes #3595.
@teknium1 teknium1 merged commit 0a80dd9 into main Mar 29, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant