I was frustrated with the buggy code generated by current code assistants. I spend too much time fixing their errors, even obvious ones. If they get stuck on an error, they suggest the same buggy solution to me again and again and cannot get out of the loop. Even LLMs today can discover new algorithms; I just cannot tolerate that they cannot see the errors.

So how can I get them out of this loop of wrong conclusions? I need to feed them new, different context. And to find the real root cause, they should have more information. They should be able to investigate and experiment with the code. One proven tool that seasoned software engineers use is a debugger, which allows you to inspect stack variables and the call stack.

So I looked for existing solutions. An interesting approach is the MCP server with debugging capability. However, I was not able to make it work stably in my setup. I used the Roo-Code extension, which communicates with the MCP server extension through remote transport, and I had problems with communication. Most MCP solutions I see use stdio transport.

So I decided to roll up my sleeves, integrate the debugging capabilities into my favorite code agent, Roo-Code, and give it a name: Zentara-Code.

Zentara-Code can write code like Roo-Code, and it can debug the code it writes through runtime inspection.

My previous discussion regarding Zentara is here: https://www.reddit.com/r/LocalLLaMA/comments/1l1ggkp/demo_i_...

I would love to hear your experience and feedback. It would be great if you could test it in different languages.

Documentation: zentar.ai

Github: github.com/Zentar-Ai/zentara-code/

VS Code Marketplace: marketplace.visualstudio.com/items/?itemName=ZentarAI.zentara-code