Bug: Eliza UI interface agent sends double response to single comment

[mihai169]

Agent sometimes sends two replies for one user comment - must send one reply to one comment or a continuation of 
first reply not two separate replies to same comment.

Acceptance Criteria:
Single Reply Per User Comment:

The system should ensure that for each user comment, the agent sends only one reply.
If the agent’s response requires multiple parts, the agent should send a continuation or a single message, not separate, independent replies.
There should be no duplicate replies to the same user comment.
Continuations (if applicable):

If the agent needs to send multiple parts as a response (e.g., for long or complex messages), the agent should send a continuation reply (e.g., "Continued...") within a single thread or response, rather than sending separate messages.
Bug-Free Behavior:

The system must handle edge cases where duplicate replies could be sent, ensuring that only one reply is sent per comment.
Error Handling:

The system should detect and prevent any accidental or unintended duplicate replies from being triggered.

Gherkin-Style Test Case:

Feature: Preventing Duplicate Replies to User Comments

As a user,
I want the agent to reply only once to my comment,
So that I don't receive multiple separate replies to the same message.

Scenario: Agent sends only one reply per comment
Given a user has submitted a comment to the agent
When the agent processes the comment
Then the agent should send only one reply to that comment
And no duplicate replies should be sent for the same comment

Scenario: Agent sends continuation of first reply (if needed)
Given the agent has started to reply to a user comment
When the reply requires multiple parts
Then the agent should send the reply as a continuation of the first message
And not send two separate replies

Scenario: Agent should not send duplicate replies
Given a user has submitted a comment and the agent has already replied
When the user comment is processed again
Then the system should not send a second reply to the same comment
And only one reply should be sent for that comment

Scenario: Preventing accidental multiple replies
Given the user submits a comment and the agent replies
When an unexpected system error or bug causes the agent to send a second reply
Then the system should detect and prevent the second reply from being sent
And the user should only receive one response to their comment

Scenario: Agent sends correct response to long comment
Given the agent is replying to a long or complex user comment
When the reply is too long for a single message
Then the agent should send a continuation message (e.g., "Continued...") within the same response thread
And the reply should not be split into multiple independent replies

[snobbee]

@mihai169 that issue was solved in the new Eliza UI using the event.preventDefault() function I saw it in one of the PR that was pushed to the upstream repo and also tested it in my tests you can find a demo here #212 (comment)

[mihai169]

I just tested, saw a double response although text was similar but not same. @snobbee

[snobbee]

@mihai169 I am trying to reproduce that issue

using the prosper agent

but it only produces a single response for each user request

[snobbee]

@mihai169 here I managed to get one instance where it produces two responses instead of one when it calls the CONTINUE action:

I will need to investigate why this is happening but it looks like it called two actions at the same time NONE and CONTINUE that are both built-in actions defined in Eliza, and both produced a message.

[mihai169]

maybe because I have prompted "please continue" and "Yeah" as response to "I can provide further insights". If it is an edge case maybe we de-prioritise.

[snobbee]

@mihai169 That change would require me to update the core components of the Eliza repo. So, I'm not entirely sure, but I think it would be best to deprioritize this for now indeed and focus on the issues or bugs introduced by our own plugins. We can always revisit it later. However, this change does need to happen at the Eliza core level.

I am moving this ticket back to Review so @jkbrooks can review the comments and we can decide during the call.

[mihai169]

yes I agree

[jkbrooks]

We'll think about this more, but I'm fine with deprioritizing for now.

[mihai169]

this is still the case for create issue action and some other examples