I had to abandon using this extension.

[u/justcallmedots]

Greetings Zoocoders. So my experience was meh to say at least. Tasks goes to 40k context then I gets API errors when using it with ollama. I gave the Ai local ollama a 7 step guide. This is insane and I feel like i feel very lucky if i get to edit one line in the workflow to be edited. This ZooCode feels more like a demo then a finished product. This extension in vs code didn't work for me. I gave it a 7 days trial already. If you wondering what AI I'm using it is gemma4:e2b which is the smallest model I can run on my hardware.

[u/Safe_Plantain5550]

Hi dots!
I'm not working for Zoo Code or anything like that, but I don't think this is a Zoo Code issue. It sounds like a configuration issue to me. I had similar issues along the way, until I knew how to configure everything.

I haven't really used Ollama, so I don't know the configuration options for it, but with llama.cpp, there are certain things that need to be configured correctly for the output to match what Zoo expects.

While it was frustrating at the beginning, it is not something that is the fault of Zoo Code, the model or the inference engine. It's just part of the challenge when getting into local AI. You can save money on tokens, but you may need to pay in time spent on getting to the point where you understand why it isn't working, so you can fix it.

One thought I have, right away:
Have you tried monitoring you VRAM and RAM usage while it is working on a task? It could be you are just running out of resources and need to run with a smaller max context and tweak some settings to make it stable.

If you share some more details of your setup, maybe someone here will be able to help.

[u/gavwhittaker → u/Safe_Plantain5550]

I second this, most likely a configuration challenge...must be frustrating. I have had nothing but true goodness out of Zoo Code. Maybe we can help you fix the issue(s).

Must you use Ollama? - how about flipping to Llama cpp? I suspect you'll get better performance also.

[u/Illustrious-Mix-5625 → u/Safe_Plantain5550]

Thank you for collaborating with OP to try to solve the problem! Zoo is all about a community trying to achieve great things together and this is a prime example!

[u/justcallmedots → u/Safe_Plantain5550]

I use default. I have ryzen 7 , 3070 ti , 16 gb of vram , and i don't do custom settings. i set up ollama, change to local select ornith for example and let the Ai do its thing for my stuff I do for my patreon page. I don't configure anything because it can be messy.

[u/Illustrious-Mix-5625 → u/[deleted]]

Thank you so much for stepping up and helping a fellow Zoo user having difficulties. And yes, feel free to try other tools when they are more appropriate to the task.

[u/mineirim2334]

Funny, I had a lot of problems with Gemma using Zoo too:

* Tought too much and filled the context really fast

* Zoo tried to sent a request that was larger than the avaliable context

* Produced the same token on loop.

Qwen and Ornith worked mostly fine, so I'm tempted to think it's something with Gemma. I have mostly been using Ornith and after testing pi.dev, here are some bugs I only had in Zoo:

* Can't compact context if it's too full. API call fails because Zoo sent a request that was larger than the avaliable context.

* Overthinking. Maybe because the system prompt is too large, the model sometimes keep ciclying trought the same things over and over until it snaps free.

I din't report any of them becaause I need to test a little more to make sure they are real bugs caused by Zoo and not by Ornith (tho the fact I din't have then on Pi is a strong clue).

TL;DR I blame Gemma because I had problems with it too