Okay, We REALY REALY need a STOP button 🔴

I saw someone else on hear had mentioned the need for a stop button. I wasn't sure at first if that was truly necessary as I have only been serious about using Agent Zero for the past 2 weeks now.

Well, it seems they were indeed correct. Today I found the need for one in the middle of my workflow. I had been doing some market research and with my agent going at it for about 30 minutes solid, I managed to fill the context.

The memory compaction kicked in and started doing its job. I have seen this before, so I thought, No big deal - research was about complete and it was running tokens on the final response.

Then, something went wrong and the memory compaction failed. It hung at that step forever. I nudged it to continue giving the final response. It seems that with the context being full it did not have reference of what was already given as output - so it proceeded to do the research as per original instructions again!

It just kept going! I paused it, I sent a stop message, the agent acknowledged but continued its tasks any way. I gave it further instructions to abort - again it acknowledged that "the user wants me to stop" but it still kept going.

It just kept burning up tokens. No way did I want it to run through the whole 30 minute research routine again! The only solution I had was to stop the docker container.

This behavior is just unacceptable. If I were using online models and required to pay API fees I could be throwing money away had I left the agent unattended. That's time and money wasted.

Thankfully, I have the hardware to run everything locally, so in this case it was just my time and the hassle to get it to stop.

Can someone perhaps bring this up in today's call? I'm unsure if I will be able to make it. Thanks. Would be nice to see this implemented in a way that stops/aborts all running tasks.

1 comment