DevoxxGenie

The deciding trait is that Agent Mode actually changes files rather than describing what you should change. It runs parallel sub-agents against a task, so a refactor that touches several corners of a module does not become four sequential conversations, and all of it happens inside the IDE where you already read diffs.

What you give up is a support contract and a roadmap somebody is paid to deliver. Pick it if free and in-editor is the combination you want. Pick Firebender when your Android team needs someone accountable.

The exposure is the command tool. It sits alongside the file and search tools as a peer, which means the loop treats running something and reading something as the same kind of step, and nothing in the published material describes a container, a command allowlist or a dry run between a model's suggestion and your terminal. That is a decision, not an oversight.

What it does right is stay inside a process you already trust. The plugin runs where your project is already open, so the credentials and paths it can reach are the ones you brought.

1. This is the correct direction of dependency. The agent is not asked to judge whether code is unsafe; a deterministic scanner makes that call and the agent is handed the result, so the finding is reproducible by anyone with the same tool and version. 2. Converting findings into ordered tasks turns a report into a plan without inserting a generative step between them.

2. No benchmark is published and none is needed, because the capability being claimed is integration, and integration is demonstrated by naming the three programs it integrates.

The ownership structure removes the failure mode that ends most tools on this board. There is no investor waiting, no burn rate, and no incentive to convert users into a meter, because the organisation behind it monetises tickets and sponsorships elsewhere. Two years of shipping is a cadence, and cadence from an unfunded project is a stronger signal than cadence from a funded one.

Moat: reputation inside a specific community, which is narrow and durable. Likely path: maintenance continues while the maintainers enjoy it. Position: the safest free bet in the JetBrains column, priced accordingly.

Procurement is a formality here: nothing to sign, nothing to negotiate, and a licence my legal team reads once. The work lands on my platform team instead, because sixty installations configured individually means sixty places a provider setting can drift and no central answer to which model touched which repository.

It does not run unattended, so it never appears in my pipeline metrics and never becomes a dependency of a build. That limits the upside and also limits the damage. Approved with conditions: managed configuration, and provider settings pushed rather than chosen.

Local-first is claimed by many and meant by few. Naming Ollama, LMStudio, GPT4All, Llama.cpp and Exo as providers alongside the hosted ones tells me somebody actually tested against hardware rather than adding a checkbox, and it means the expensive default is a choice instead of a requirement.

The server marketplace covering both transports is the other detail I care about, because it means the things I already run reach the agent without a wrapper. Permissive licence, readable Java, and a fork stays viable. Very little left to complain about.