
🧩 From AI-assisted plugin development to LSP, MCP, and new IntelliJ Platform APIs – we covered a lot at Plugin Developer Conf 2026! Couldn't join us live? All talks are now available to watch whenever you like 👇 youtube.com/playlist?list=PL…

News & tips for devs building plugins for @JetBrains products. Subscribe: jb.gg/mp-updates 🦋 bsky.app/profile/platform.je…

🧩 From AI-assisted plugin development to LSP, MCP, and new IntelliJ Platform APIs – we covered a lot at Plugin Developer Conf 2026! Couldn't join us live? All talks are now available to watch whenever you like 👇 youtube.com/playlist?list=PL…

Yup, we are doing that! @halirutan and I, live, soon!
Tonight, @hszanowski and I will stream at 21:00 UTC. We'll look into adding an MCP tool to help navigate and locate source JARs in IntelliJ Platform projects. It'll be a hacking session, and you should expect things to go wrong. Still, drop by and say hello here on X, on Twitch, or YouTube: youtube.com/@halirutan youtube.com/@hszanowski

Last talk of Plugin Developer Conf 2026: Alexander Koshevoy at 18:00 CET (17:00 UTC). Make your plugin work in every project environment. See how EelApi covers local, WSL and dev containers. Watch live 👉 youtube.com/watch?v=Wq4TrsyD…

Evgeny Kudelevsky will take the stage at 17:20 CET (16:20 UTC)! One codebase, four plugins, five services. See how to design your plugin so a second integration doesn’t mean starting from scratch. Watch live 👉 youtube.com/live/Wq4TrsyD8Jo

See that? This is a set of raffles happening online, interrupted by the JetBrains Plugin Developer Conf 2026 🤣 Come and join us NOW👇 youtube.com/live/Wq4TrsyD8Jo

Want to bring your language to JetBrains IDEs? At 15:50 CET, Vladimir Logachev shows how a small language plugin works with the native LSP API, how it’s shipped, and how to apply it to your own language. Watch live 👉 youtube.com/live/Wq4TrsyD8Jo

⚡️⚡️ Plugin Developer Conf 2026 starts in 10 min! Explore how AI is changing plugin development, discover new IntelliJ Platform APIs, and learn practical techniques from JetBrains experts and fellow plugin devs. Join the livestream 👇youtube.com/live/Wq4TrsyD8Jo…

It's Friday evening, and you surely have plans, but you can mark it on your calendar next Tuesday! Together with @halirutan and @RoboNovotny, we're hosting the Plugin Developer Conference 2026. Online! Book 🗓️ November 10, 1:00 pm UTC, and join us and seven more speakers!! Remember to register so you don't miss it: jb.gg/PluginDevConf2026
Join the Plugin Developer Conf 2026 Keynote and see what’s new: 🧩 Ivan Chirkov: Marketplace updates 🛠 @hszanowski: Gradle Plugin & DevKit ✅ @RoboNovotny: Plugin Verifier 🚀 @Yuriy_Artamonov: IntelliJ Platform 🗓️ Nov 10 | Free and online Register 👉 jb.gg/PluginDevConf2026

🧩 Using AI to build a plugin? Learn from someone who did. At Plugin Developer Conf 2026, Mark Paluch shares where AI helped him build Dependency Assistant, where it added work, and how to keep control of your code. 🗓️ Nov 10, 15:10 CET Register 👉 jb.gg/PluginDevConf2026

Did everyone forget that it was just 5 minutes ago that we were still hunting on Stack Overflow for a solution to this one bug we couldn’t solve?? Why can’t we have a more rational view of what remains when you strip away the hype around large language models, agents, and tooling? With the right setup, even cheap or local models make a developer's life so much easier. This week, I worked on the parser for the IntelliJ Wolfram Language plugin. When I started this project in 2012, there wasn't much information about the language, let alone a complete grammar. Most of the knowledge came from scattered documents and lots of discussions with other developers. I knew my implementation was good enough for the plugin, but it still had many quirks and gaps. So I used Wolfram’s CodeParser, an awesome project mainly developed by Connor Gray and Suman Banerjee, as my Ground Truth. I wrote a small adapter for my plugin’s structure and a wrapper around CodeParser's CLI to connect it to my plugin's unit tests. With that in place, I could use CodeParser's many test cases to compare results and identify differences. The agent could then work through the necessary fixes step by step. The Baseline made all the difference. The agent had something concrete to work against, and I could see when it went off track. Now, there are 421 passing unit tests, each checking a specific case against the baseline Wolfram parser. I could have done this manually, but I estimate going through every reported difference and fixing it would have taken me weeks or months. I used OpenCode as an agent inside the IDE through the Air plugin. The model was GPT-6.1 Sol, which is much cheaper than other frontier models like Astra. Reasoning was high for the planning and medium for the implementation and the rest. I made sure the agent knew how to navigate the attached SDK sources, had access to a research subagent to find information about the IntelliJ Platform, and knew how to interact with the IDE to run inspections, reformat, and use all the other MCP tools. The whole thing used around 410 million tokens, of which 400 million were cache reads, and 6.5 million were cache writes (which means they were really cheap). That came to around $70 for my actual usage, which is OK given how much work has been done. For comparison, based on the same token breakdown, I estimate it would have cost roughly $550 with GPT-6 Astra. I’m sure that with smaller steps and maybe more guidance, this could have been done with a local Qwen model. I think a lot of it comes down to knowing your tools. As a developer, you need to understand what you're asking the agent to do, how to give it the right tools, and, most importantly, how to check whether it actually did the right thing (yes, you can and should interrogate your agent about its own work; try it). Otherwise you're just hoping for the best.

Join the Plugin Developer Conf 2026 Keynote and see what’s new: 🧩 Ivan Chirkov: Marketplace updates 🛠 @hszanowski: Gradle Plugin & DevKit ✅ @RoboNovotny: Plugin Verifier 🚀 @Yuriy_Artamonov: IntelliJ Platform 🗓️ Nov 10 | Free and online Register 👉 jb.gg/PluginDevConf2026

The @TornadoVM team dropped me a message about TornadoInsight, their free plugin for @IntelliJIDEA for working with Java on GPUs. A nice find to pass along if you’ve been curious about GPU programming in Java 👇 plugins.jetbrains.com/plugin… Have you folks already worked with GPUs?

💡 Get inspired by developers from SAP and Broadcom, JetBrains experts, and independent plugin authors at Plugin Developer Conf 2026! 🗓️ November 10 | Free and online Discover practical insights from people building real-world plugins. Register 👉 jb.gg/PluginDevConf2026

There are people burning tokens to rewrite IntelliJ IDEA in Rust, so it starts faster. Then you find out it's TypeScript under the hood. 0.9s? Hold my beer! This is from our internal channel today. IJ with performance improvements we work on. 818ms.

My AI agents have pets now!! 🐾 Air Pets gives each Air session a companion in your @JetBrains IDE See when agents are working, need input, or are ready for review. Click a pet to open its conversation. Hover for session details, drag it out of the way, or check the current spending in a blast! ⚙️ Settings → Plugins → "Air Pets" (requires Air @getsome_air ). youtu.be/UWTrIgsxAaE

JetBrains Plugin Developer Conf 2026 is coming! 🗓️ November 10, 1:00 pm UTC | Free and online Explore the shift toward AI-powered plugin development, ACP, MCP, LSP, new IntelliJ Platform APIs, and practical lessons from plugin developers. Register 👉 jb.gg/PluginDevConf2026