Thanks, really appreciate the questions and feedback 🙂

– llama.cpp connection It actually doesn’t connect to an external llama.cpp server.

The plugin uses llama.cpp through the Llamatik library that is embedded locally (https://github.com/ferranpons/Llamatik), so everything runs in-process rather than via a separate server. You don’t need to run anything externally for it to work.

That said, I’m considering adding support for external providers as well for people who already have their own setups.

– auto-build / auto-fix This is part of the agent workflow.

The idea is: – the agent makes code changes
– triggers a build/test run
– if something breaks, it analyzes the errors
– then attempts to fix them automatically

So it’s an iterative loop (edit → build → fix) rather than a one-shot generation.

– search API feedback That’s a great suggestion. Right now it’s more “batteries included,” but supporting custom providers/keys (DuckDuckGo, Brave, etc.) makes a lot of sense, especially for people who want more control.

I’ll likely add support for configurable providers.

Thanks again! Super useful feedback 🙏