A fast fix for the "double reply" loop in Discord when your agent posts the same answer twice.
This usually looks like: one user message, then two near-identical bot responses. It feels random, but it’s often a policy or routing overlap problem, not a model-quality issue.
The bot receives the same event from two paths (or two active responders) and processes both.
I’m seeing duplicate replies. Diagnose before changing anything.
Step 1) Show current response policy settings relevant to Discord replies.
Step 2) Confirm there is only one active responder path for this channel/thread.
Step 3) Propose the smallest fix to prevent duplicate responses.
Step 4) After applying fix, run one clean-room test and return proof:
- test channel/thread used
- input message
- exact output count (must be 1)
- timestamp + timezoneIf a legacy bot and your current agent both listen to the same messages, users can see what looks like a duplicate answer.
Mixed rules can create accidental double-processing in noisy channels. Pick a single clear trigger mode for testing.
Settings can look correct in files/UI while the old runtime behavior is still active. Restart, then retest in a clean channel.
If messages are mirrored or forwarded between thread contexts, the same user input can be handled more than once.
During diagnosis, force a single trigger path: one bot, one channel, one mention policy, one test message.
Don’t keep changing multiple settings at once. Make one change, restart, run one test. Otherwise you can’t tell what fixed it.