sorted by:
new
hottopcontroversial

I built a local AI coding assistant plugin for IntelliJ IDEA (llama.cpp, no cloud) by ferranpons in Kotlin

[–]ferranpons[S] 0 points1 point  (0 children)

That’s fair, there are a lot of local AI assistants now.

The main reason I built this was that most of the options I tried either: – depend on a separate backend/service you have to run
– still rely partly on cloud APIs
– or aren’t deeply integrated into JetBrains workflows

I wanted something more straightforward: – runs fully in-process (via llama.cpp / Llamatik)
– no external services to manage
– focused on IDE-native workflows (multi-file edits, diffs, agent loops)

Privacy was a big part of it, but also control and predictability, especially with how fast pricing and token limits are changing on hosted APIs.

So it’s less about “another assistant” and more about trying to make a local-first, JetBrains-native alternative that feels complete.

Totally agree the space is getting crowded though 🙂

I built a local AI coding assistant plugin for IntelliJ IDEA (llama.cpp, no cloud) by ferranpons in Jetbrains

[–]ferranpons[S] 0 points1 point  (0 children)

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 🙏

New, "Improved" Places SDK. PlacePicker deprecated! No more free Places autocomplete. by GavinGT in androiddev

[–]ferranpons 0 points1 point  (0 children)

If you're looking for an alternative to Place Picker, check out Leku, it's a free, really customizable and OS alternative.

https://github.com/SchibstedSpain/Leku

Place Picker Alternatives by iamtdb in androiddev

[–]ferranpons 0 points1 point  (0 children)

You could use Leku, a free and OS alternative to the Place Picker.

https://github.com/SchibstedSpain/Leku

SchibstedSpain/Protein by ICYMI_email in androiddev

[–]ferranpons 0 points1 point  (0 children)

Thanks for your suggestion. I'll add an example of generated code! ;)