JetBrains Air in RubyMine - one place to run your agents and verify their work
- As of this release, JetBrains IDEs ship with Air, a new layer for agentic development. Work with the coding agents of your choice, and run, track, and verify multi-agent workflows inside your IDE – where code intelligence helps agents make fewer wrong turns and gives you the tools to review every change before it ships.
- Your agents, your models, your subscriptions
- Air works with Claude Agent, Codex, Gemini, GitHub Copilot, Junie, OpenCode, and other ACP-compatible agents. It detects the agents already installed on your machine so you can connect them in a click, and you can add more from the agent registry.
- Your existing setup carries over, too: Provider subscriptions, API keys, and even a custom base URL all work, with no JetBrains AI subscription required. Run Claude Agent on your Claude subscription in the terminal or in a full-screen IDE tab, use other agent subscriptions in the chat or terminal, and switch between subscriptions at any moment, even mid-session.
- A central workspace to review changes and guide the agent
- Review an agent's changes with the surrounding code and your project tools in view, and send feedback straight back to the agent. Anchor a note to a specific line in the diff, or comment directly from the code, so the agent gets concrete context about the change you want. Work in the chat or the terminal, whichever suits you.
- Free AI agent with Junie Lite
- Air includes free AI with the Junie Lite configuration, so you can use an agent without a subscription. You only need a JetBrains Account.
Native mode for WSL and Dev Containers
- Why Native mode?
- Native mode lets you work on projects in WSL and Dev Containers using your locally running RubyMine, while your code and development tools stay inside the Linux environment. A lightweight agent handles file access and process execution, improving performance and providing correct handling of Linux paths and symbolic links. There's no need to install a full IDE backend inside the environment or open a separate remote development client.
- Opening projects natively
- For WSL projects, JetBrains recommend using File | Open and selecting your project folder in the WSL file system. RubyMine opens the project in Native mode automatically.
- For Dev Container projects, enable Open dev container projects natively in Settings | Advanced Settings, then use Connect to Remote on the Welcome screen to open your project.
- Native Ruby interpreters
- RubyMine 2026.3 introduces native Ruby interpreters that use the same infrastructure to run Ruby inside your project's environment. Your Ruby installation stays where it is. What changes is how RubyMine accesses it and runs your tools. In WSL projects, interpreter lists are also scoped to the environment, keeping WSL interpreters separate from Windows, Docker, and SSH configurations.
- Native WSL interpreters are enabled by default for new users. Users with existing remote WSL interpreters keep their current configurations and can switch to native interpreters in Ruby settings. Legacy remote interpreters remain available during the transition, with retirement planned for a future release. In Dev Containers opened in Native mode, native Ruby interpreters are enabled automatically, with no separate Ruby setting required.
Ruby
- Smarter Ruby interpreter selection
- Setting up your project's Ruby interpreter is now easier with the following improvements:
- Gemfile-aware selection - Interpreter selection now takes the requirements in your Gemfile’s ruby directive into account, including exact versions, minimum and maximum versions, and pessimistic (~>) constraints. Dedicated version files, such as .ruby-version, take priority. If multiple installed interpreters match, RubyMine asks you to choose.
- Automatic Homebrew detection - Ruby interpreters installed via Homebrew are detected automatically, so you can select them without manually specifying their paths.
- Improved heredoc editing
- This release brings more consistent indentation when editing heredocs:
- Pressing Enter after a heredoc opening or within its body applies the appropriate indentation for <<~, <<-, and <<.
- Indentation works on consecutive blank lines as well.
- For basic (<<) heredocs, the closing delimiter stays at the beginning of the line.
- For <<~ and <<-, pressing Backspace before an over-indented closing delimiter aligns it with the opening line instead of joining it to the preceding content. This also works in ERB templates.
- Clearer diagnostics for RuboCop launch errors
- RubyMine now clearly identifies unsupported shell scripts used to launch RuboCop. If your project's bin/rubocop is a shell wrapper that RubyMine cannot use, the IDE displays a RuboCop binstub is not a Ruby script message with details to help you resolve the configuration issue, replacing the cryptic No Ruby script found in input error.
Rails
- Support for ActiveSupport load hooks
- RubyMine now understands ActiveSupport.on_load and ActiveSupport.run_load_hooks, recognizing modules included through these hooks and the constants they make available.
- This improves constant resolution in Rails applications, avoiding incorrect unresolved-reference warnings. When you insert a constant through code completion, RubyMine can also shorten its qualified name where the namespace is no longer needed.
- Support for the Rails query command
- Use rails query through Run Anything or with completion in the terminal to run Active Record queries or raw SQL, inspect database schemas, list models, and view query execution plans.
- For example, run rails query "User.count" to get the result as structured JSON, or rails query schema users to inspect the users table.
Code insight
- Improved navigation to Ruby classes and symbols
- Go to Class and Go to Symbol now support fuzzy matching across nested class, module, and constant names. For example, typing ActRecBase finds ActiveRecord::Base. Constants also appear alongside classes and modules in Go to Class.
- Search results now consistently show the containing class or module and the file path, making it easier to distinguish declarations with the same name.
- These improvements use the symbol-based modeling engine, which is enabled by default in RubyMine.
- Safer Rename refactoring
- Renaming is now safer. When you rename a global variable, class, module, or constant, RubyMine warns you if the new name would conflict with an existing one, so you can fix it before anything breaks. You'll also be alerted to invalid characters and reserved names like $? and $@.
- Clearer breadcrumbs in Ruby files
- Ruby breadcrumb naming now aligns with the navigation bar, preserving namespace prefixes such as Bar::Baz and leading :: in absolute references. They also include constant and global variable declarations, display singleton classes as << self, and provide tooltips.
- Code blocks now show just the final method name, such as bar for foo.bar { ... }. By default, breadcrumbs are shown only when Show Members is disabled in the navigation bar, reducing duplicate navigation elements.
Other noteworthy improvements
- Sound cues for IDE events and editor line marks
- Screen reader users now get audio cues for editor line marks: errors and warnings, lines added, changed, and removed under version control, and code folding. You can also hear when things finish. Builds, tests, and other time-consuming background tasks report their results with distinct sounds for success, warning, and error states, and breakpoint hits come with a sound too. And if you work across multiple monitors or several projects at once, enable these sounds so you don't have to glance at the screen to check statuses.
- You can explore and preview the sounds on the new Accessibility settings page, and use the Play sound checkbox on the Notifications settings page to enable cues for a specific notification group.
- Automatic error and freeze reporting
- RubyMine 2026.3 automatically sends error and UI freeze reports to JetBrains, helping us identify the problems that interrupt your work and prioritize fixes based on their impact.
- Reports contain only technical data – personal details, such as file paths, URLs, and usernames, are removed from report messages before they leave your machine. You can turn automatic reporting off in Settings | Appearance & Behavior | System Settings | Data Sharing.
- Git worktrees for parallel work and easy code reviews
- RubyMine 2026.3 can now copy your local project configuration into new Git worktrees, including run configurations and other settings stored in .idea. You no longer need to commit those settings to Git or recreate them for each worktree.
- You can also list local and ignored files in .worktreeinclude for the IDE to copy, and configure a custom script to run when a worktree is created, for example, to install dependencies.
- Other worktree improvements include:
- Support for multi-root projects.
- More reliable worktree creation in repositories with submodules.
- The option to check out a branch that is already in use in another worktree, using --ignore-other-worktrees.
- Automatic removal of deleted worktrees from Recent Projects.
- Improved support for WSL and container-based projects.
Discontinued features
- Capistrano, Puppet, and Chef
- RubyMine 2026.3 removes the remaining support for Capistrano, Puppet, and Chef. Usage of these integrations was very low, and Capistrano has largely been replaced by Kamal for deploying Rails applications.
- Capistrano: The Capistrano run configuration and predefined task support have been removed. Only the minimum functionality needed to detect Capistrano projects remains.
- Puppet and Chef: These plugins are no longer maintained and are incompatible with RubyMine 2026.3. If either is installed, the IDE displays a compatibility notification. You can disable or uninstall the affected plugin.
- Vagrant
- RubyMine no longer bundles the Vagrant plugin or offers Vagrant when adding a remote Ruby interpreter. You can no longer create new Vagrant interpreters.
- Existing Vagrant interpreters remain in your interpreter list. To continue using them, install the Vagrant plugin from JetBrains Marketplace. Vagrantfiles are still recognized as Ruby files.