RubyMine 2025.2 brings several exciting updates, including:
Let’s dive into the details!
JetBrains AI Assistant just got a major upgrade, giving you smarter completions, better project understanding, and more control over how AI works in your IDE. Below is a brief overview of AI Assistant’s new features. Read the full article here.
Cloud-based code completion for ERB has been expanded. It now works within ERB tags, such as <% <caret> -%> and <%= <caret> %>.
This feature builds on RubyMine’s existing AI-based code completion for Ruby and includes enhancements like:
AI Assistant chat now leverages the Search Everywhere functionality for Classes and Symbols to incorporate more accurate context.
You can now define project-specific instructions that guide AI responses, such as coding style or framework constraints. Rules are stored inside your project and can be shared across the team, ensuring alignment and consistency without repeated manual input.
AI Assistant allows you to work with local models by connecting third-party LLMs running on your machine. In addition to Ollama and LM Studio, you can now use any model server compatible with the OpenAI API, such as llama.cpp, LiteLLM, and others. This lets you take advantage of AI-powered features for free, with no data leaving your machine.
JetBrains AI Assistant now supports image attachments in the chat when using Anthropic and OpenAI models.
In RubyMine 2025.2, AI Assistant will deliver more code suggestions across a wider range of contexts, streamlining your development workflow.
Additionally, improvements to the formatting of multiline outputs provide a more refined coding experience.
Junie, the JetBrains AI coding agent available in RubyMine 2025.2 as a plugin, features the following major updates:
RubyMine 2025.2 allows you to disable specific type signature providers used for certain code inspections.
This can be particularly helpful in cases where an inspection uses data from a few services and you want to avoid conflicts between them.
For example, the Mismatched Argument Type inspection uses RBS and Sorbet, which might conflict with each other. To avoid any issues, you can disable one of them.
To find all inspections with potential conflicts and disable some of their providers, go to Settings | Editor | Inspections | Ruby | Probable bugs.
Working with Rails projects that contain numerous migration files is now much more fluid. RubyMine 2025.2 ensures that edits, additions, and deletions of migrations happen without delays or freezes, keeping your workflow uninterrupted.
We’ve optimized how certain background tasks are handled during project startup.
By delaying some operations and reducing how often others run, we’ve made project startup quicker and smoother, allowing you to get started on your work faster.
For instance, operations like refreshing Rake tasks and Rails generators or updating RBS collections now run only when strictly necessary.
RubyMine 2025.2 now supports hover hints for RBS declarations and references.
Press Ctrl and hover over a declaration in an .rbs file to see a preview of the target.
This preview is particularly helpful for quick, in-context insights into a reference's target. For example, you can use it to view the definition of a type alias without navigating to it.
Improved type support with RBS Collection is now enabled by default.
You’ll notice improved precision in features such as:
Note: The RBS Collection integration requires RBS 3.2, which comes bundled with Ruby 3.4. If you're using an older Ruby version, RubyMine will prompt you to install the appropriate gem.
RubyMine 2025.2 comes with improvements for Bundler that are especially beneficial for multimodule projects.
RubyMine now groups missing gem notifications across all modules into a single alert, reducing clutter and interruptions.
To save you from dealing with dialogs each time you invoke a Bundler command, we’ve introduced a new Bundler tab. Located under Settings | Tools, it allows you to:
RubyMine now installs gems one module at a time to prevent conflicts and avoid reinstalling gems shared between multiple modules.
We’ve optimized how RubyMine handles code completion for exception constants. In cases where no prefix is provided (for example, when triggering autocompletion without typing), the suggestions are now limited to a focused set of relevant constants.
This adjustment significantly boosts performance, especially in large projects.
In RubyMine 2025.2, the process of installing debugger gems is non-modal, with progress displayed in the terminal window instead of the progress bar.
RubyMine powers the newly introduced Ruby linter in Qodana.
The Ruby linter brings RubyMine’s robust code inspections into automated workflows, helping you catch issues and maintain high code quality across your projects.
Qodana for Ruby is currently in Early Access. You can find more details in the Qodana documentation.