Repository navigation
[BUG] zoo code stuck after that run process #622
Description
Describe the bug
i have a issue, when i use zoo code, it's stuck often after that agent run process!
Expected behavior
expect to not stuck and continue to work after that running process is closed!
Screenshots
What version of zoo are you running
3.60.0
Activity
[-][BUG] zoo code stuck![/-][+][BUG] zoo code stuck after that run process[/+]pajitosingh commentedon Jun 16, 2026
Same issue here. Running 3.60 on vs code 1.124.2
Have tried entering "echo" as as well as just hitting enter a couple of times in the terminal. This sometimes kicks it back into working, at least on the first occurance, but can get stuck immediately on next run command. Very frustrating, and something that seems much worse recently. Previously it was possible to just hit the 'x' on the run command itself, but now even that does nothing. Any further commands issued to zoo goes into "queued messages". Has basically put a total stop to use and development with zoo code, having previously put over 1.4B tokens through it over last month.
onlineapps-cloud commentedon Jun 16, 2026
yes, issue appear when agent execute some like:
ls -la && echo DONEpajitosingh commentedon Jun 16, 2026
This seems to happen most likely with stuff that completes very fast. Maybe it would be a good idea to add a bit of a delay (like with file saving) after any terminal command or something so that stuff that runs nearly instantly doesnt lock up like this? Don't know the internals of how this works so just taking a stab in the dark.
pajitosingh commentedon Jun 16, 2026
For anyone else this helps, a pathetic but working method:
-Turn off 'Execute' from auto-approved.
-For every command, copy paste into terminal and run.
-Send terminal output manually back to context.
Voila, it works but sucks. At least now able to get some work done, but ho boy it would be nice if didn't have to do this.
pajitosingh commentedon Jun 19, 2026
Another work around btw was just to instruct Code mode to add "sleep 5". Still absolutely not bulletproof.
Currently running 3.62 and can confirm STILL having terminal bug! It's much less common now, but still happening!
Don't know if related, but getting "1 file and 0 cells to analyze" message forever going on the bottom of vs code (1.125).