Bug: When aborting and sending a new message the agent ignores the new message and starts processing the previous user message. #2270

Activity

1. ezynda3

   changed the title [-]Bug: When aborting and sending a new message the agent ignores the new message starts processing the previous user message.[/-] [+]Bug: When aborting and sending a new message the agent ignores the new message and starts processing the previous user message.[/+] on Aug 27, 2025
2. github-actions commented on Aug 27, 2025

   

   github-actionsBot

   on Aug 27, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Are interrupted messages lost from the context? #2171: Discusses whether interrupted messages are lost from context and similar behavior where aborted messages affect subsequent processing
   • Queued message not running #2246: Reports queued messages not running properly, where messages get ignored or don't process as expected

   Feel free to ignore if none of these address your specific case.
3. rekram1-node commented on Aug 27, 2025

   

   rekram1-node

   on Aug 27, 2025

   Contributor

   More actions

   @ezynda3 are you referring to this?

   Glob “**/zksync/*Eco*.sol”
   No files found
   

   there is none

   I'll update the EcoFacet.sol to use "portal" instead of "intentSource" for naming consistency, then update the deploy scripts.
   
4. ezynda3 commented on Aug 27, 2025

   

   ezynda3

   on Aug 27, 2025

   ContributorAuthor

   More actions

   Yes
5. rekram1-node commented on Aug 27, 2025

   

   rekram1-node

   on Aug 27, 2025

   Contributor

   More actions

   To me it looks just like prompting issue tbh, I will test to make sure but if the llm is in a loop and you break it will only a few words I dont know how much it will respect that instruction
6. rekram1-node commented on Aug 27, 2025

   

   rekram1-node

   on Aug 27, 2025

   Contributor

   More actions

   Yeah just tested, @ezynda3 this is just a prompting issue, the LLM likely needs a bit more of a prompt to steer it off the loop it was already doing.

   Closing since this isn't on our end
7. rekram1-node

   closed this as completedon Aug 27, 2025