fix(queue): deduplicate followup queue entries

[samratjha96]

Was facing some issues with multiple responses to my questions on Discord. Did some digging with Claude and it's because Discord seems to fire off multiple events if the previous one took a while to get processed.

I think this is a safe assumption to always drop the EXACT same message from being enqueued if it's already in the queue. Didn't test with other providers tbf but seems like the right behavior

Summary

• Add exact-match deduplication to the followup queue to prevent duplicate responses
• Extracted isPromptAlreadyQueued() helper for clarity

Problem

When messages arrived while the agent was busy processing, the same message could be enqueued multiple times into the followup queue. This caused the bot to respond to the same user message 2-4+ times.

Root cause: Discord's event system can emit the same message multiple times (e.g., during reconnects or slow listener processing), and the followup queue had no deduplication logic.

Solution

Add simple exact-match deduplication in enqueueFollowupRun(): if a prompt is already in the queue, skip adding it again.

Changes:

• src/auto-reply/reply/queue.ts - Added isPromptAlreadyQueued() helper
• src/auto-reply/reply/queue.collect-routing.test.ts - Added test coverage

Testing

• pnpm lint
• pnpm build
• pnpm test
• Manually verified on Discord: single response per message even when multiple events fire

Closes: #598

[thewilloftheshadow]

The prompt from Discord does include the message ID in it, so if a user truly wants to send the same message multiple times that will still work

[samratjha96]

The prompt from Discord does include the message ID in it, so if a user truly wants to send the same message multiple times that will still work

There's an envelope created in https://github.com/clawdbot/clawdbot/blob/main/src/auto-reply/envelope.ts#L26-L36 that includes the timestamp so the prompt ends up looking like:

[Discord Guild #channel 2026-01-09T17:10Z] Hello world
[from: username user id:456]

The [message_id: xxx] seems to be added separately by: https://github.com/clawdbot/clawdbot/blob/main/src/auto-reply/reply/body.ts#L33-L38 but only when the message runs through the main path!! not when it's queued.

Not disagreeing because we are saying the same thing :) just wanted to mention that's what i ended up finding.

Duplicate events for the same message -> same timestamp -> same prompt -> deduplicated
User sends same text twice -> different timestamp -> different prompt -> both processed

I think the key ends up being the timestamp

[steipete]

Landed via temp rebase onto main.

• Gate: pnpm lint && pnpm build && pnpm test
• Land commit: d3a0114
• Merge commit: fb989cd

Thanks @samratjha96!

[samratjha96]

⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣀⣤⣴⣶⣶⣶⣤⣄⡀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣴⠿⢋⣉⠀⠀⠀⠀⠀⠉⠻⣷⡀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢠⡿⠋⠀⢾⣿⡆⢠⣾⡿⢿⣦⢸⣿⣷⡀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣿⠁⠀⠀⠈⠉⠀⣾⡏⠀⠈⣿⡇⠀⠹⣷⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣸⡟⠀⠀⠀⠀⠀⠀⢿⣇⠀⠀⣿⡇⠀⠀⢻⡇⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⢰⣿⠀⠀⠀⠀⠀⠀⠀⠘⣿⣆⣰⣿⠃⠀⠀⣸⡇⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⣰⣿⣿⠀⠀⠀⠀⠀⠀⠀⠀⠘⢿⣿⠃⠀⠀⢀⣿⠁⠀⠀
⠀⠀⠀⠀⠀⠀⢀⣼⠟⠀⠻⣷⡀⠀⠀⠀⠀⠀⠀⠀⠈⠃⠀⠀⠀⣾⠇⠀⠀⠀
⠀⠀⠀⠀⠀⣰⡿⠋⠀⠀⠀⠘⠿⣶⣤⣤⡄⠀⠀⠀⠀⠀⠀⠀⢸⡿⠀⠀⠀⠀
⠀⠀⠀⣠⡾⠋⠀⠀⠀⠀⠀⠀⠀⠀⠉⠉⠁⠀⠀⠀⠀⠀⠀⠀⢸⣇⠀⠀⠀⠀
⠀⠀⣼⡟⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠘⣿⡀⠀⠀⠀