I hope I’m not doing anything wrong but I gave zoo.dev desktop 2 really simple stl files (online tool declares both are "Complexity Classification:Low" and asked it to make kcl’s. It’s been “reasoning” for 26 minutes and still going! I thought I could do a lot in 400 reasoning minutes a month ($99/year) but I’m watching my monthly minutes just drain away.
OK it finally stopped after 28 reasoning minutes and did a horrible job. One of the 2 results looks NOTHING like the model I gave it.
I don’t want to keep giving it what I think are simple things and have it take 7% of my monthly minutes every time just to hand me back something very wrong.
Below is what I asked it to convert to KCL and its result. A waste of 28 reasoning minutes for sure. Help! I can’t see that I did anything wrong but… maybe? Help?!?
+1, just so you know it’s not just you experiencing these issues, and I’m glad it’s not just me.
I spent the better part of my workday refreshing Zookeeper/Studio (which I have a separate topic on) and rewriting instructions, failing to get very basic shapes to output.
The slow/bad outputs + losing unlimited balance that I specifically got a Pro plan for is not a good user experience.
I am trying the MCP route and hoping Claude can create some skills to work around zookeeper reasoning since I suspect that is the primary issue here.
Hello @Hackzoo! Thank you for reporting this issue. After some investigation by our devs, it was discovered that the slowness you were seeing with reasoning was due to an engine issue, which is now resolved. This was causing the modeling commands to stall, which unfairly added time to your computations.
For that, we have added 30 minutes of reasoning time back to your account. The one-time minutes do not expire, and are used when your monthly minutes are used up.
If you continue to see delays, please do not hesitate to inform us
