If you have ever built a plugin for a JetBrains IDE, you have probably encountered a moment of confusion: do you use the generator inside the IDE, or the GitHub template? Both existed, both did slightly different things, and neither one felt like the obvious right answer. That double-path setup is gone now. With IntelliJ IDEA 2026.1, JetBrains introduced a new web-API-based IDE plugin generator that replaces both the old in-IDE wizard and the IntelliJ Platform Plugin Template on GitHub[reference:0].
Two approaches, twice the work
The old system worked, but it came with real costs. The IDE generator lived inside the Plugin DevKit plugin. Any update to the template required a new release of that plugin. Even if JetBrains shipped an update quickly, many users did not immediately upgrade their IDE or Plugin DevKit version, so they kept using stale templates for months[reference:1]. Meanwhile, the GitHub template offered preconfigured workflows, issue templates, and Dependabot setup — features the in-IDE generator lacked. But the in-IDE generator let you pick additional dependencies like LSP support or Database Tools integration, which the GitHub template did not offer.
Maintaining two separate paths doubled the work for the JetBrains team. Every platform release or change to the default plugin setup meant updating templates in two places. And for developers, the choice between the two options was never clear. Many spent unnecessary time learning the differences and deciding which one to use[reference:2].
A unified approach
The new generator solves these problems by pulling the template from a web API rather than bundling it with the IDE[reference:3]. The IDE client — available from File | New Project in IntelliJ IDEA 2026.1 with Plugin DevKit installed[reference:4] — looks and feels almost identical to the old version, but with one key difference: it fetches the latest template directly from the API. Users get updated templates without having to update the Plugin DevKit plugin. No more stale templates. No more waiting for a new IDE release to get the latest plugin scaffolding.
JetBrains also launched a web-based generator that works outside the IDE entirely. You can select the plugin type (regular plugin or theme), choose features like GitHub Actions workflows or remote development support, browse project files to see how your selections affect the output, and download the generated project with a single click. The web client offers the same functionality as the IDE version, making it accessible to anyone with a browser.
What the new generator includes
The new tool combines the best features from both old approaches. It includes the GitHub integration that was previously only available through the template — workflows, issue templates, and Dependabot configuration. It also preserves the ability to select additional dependencies, a feature that was unique to the in-IDE generator. A new option under the "Remote Development" group generates plugins ready for remote development scenarios. The README.md file now includes instructions for connecting the project to a GitHub repository, closing the loop between project creation and version control.
What comes next
JetBrains plans to expand the generator gradually. Future updates may include better setup for reporting plugin issues locally or on CI/CD servers. The team is also watching how developers use the new tool and what features they ask for. If you have tried the new generator — either in the IDE or on the web — the JetBrains team wants to hear from you. The comments section and the forum are open for feedback.
For plugin developers, this change matters because it removes friction from the very first step of building something. The old two-path system created confusion and inconsistency. The new unified generator makes plugin creation feel like part of the IDE experience, not a detour from it. And that is exactly the kind of improvement that makes a difference over the long run.