Skip to content

fix(discord-bot): stop posting the same Grok answer twice - #486

Draft
omegent-app[bot] wants to merge 1 commit into
fork/devfrom
fix/discord-no-duplicate-finals
Draft

omegent-app[bot] wants to merge 1 commit into
fork/devfrom
fix/discord-no-duplicate-finals

Conversation

@omegent-app

@omegent-app omegent-app Bot commented Sep 23, 2026

Copy link
Copy Markdown

Grok/ACP often opens a second assistant id with the same body. Discord treated that as a new bubble, posted another final, and the stats footer (37s · 149k vs 31s · 157k) meant accept-without-ack could not adopt the first message.

Drop later assistants whose text matches the already-posted final, collapse consecutive duplicate bubbles, and ignore stats/T3 footers when matching an already-landed Discord final.

grok-4.6 / Grok harness

opened by Patrick Roza in chat thread Discord · Stop echoing Grok runtime_info · T3 (.)

Grok/ACP often opens a second assistant id with the same body. Discord
treated that as a new bubble, finalized again, and the stats footer
changed so accept-without-ack could not adopt the first post.

Drop later assistants whose text matches the already-posted final,
collapse consecutive duplicate bubbles, and ignore stats/T3 footers
when matching an already-landed Discord final.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants