---
title: "The Evolution of WSL Support in JetBrains IDEs"
description: "JetBrains IDEs have supported WSL through several architectures, but the 2026.2 release makes Native mode the recommended entry point for projects stored there. In Native mode, the Windows IDE delegates filesystem and process operations to the Rust-based IJent agent inside WSL, with EelApi abstracting local and remote environments for IDE and plugin code. Earlier approaches included 9P filesystem access, WSLg, and Remote Development, with problems involving symlink handling, latency, GUI limitations, installation overhead, and client–backend communication costs. Performance tests on a cold first open of spring-framework measured Native mode at 11.5 seconds to become ready versus 18.5 seconds for 9P, while project-tree scanning took 3.7 versus 8.1 seconds. Remote Development remains available, but direct project opening is now preferred in IntelliJ IDEA, WebStorm, and PhpStorm."
---

# The Evolution of WSL Support in JetBrains IDEs

[Jetbrains](https://yomu.fyi/company/jetbrains) · Kristina Pchelintseva · Sep 9, 2026

**Type:** Explainer

## Summary

JetBrains IDEs have supported WSL through several architectures, but the 2026.2 release makes Native mode the recommended entry point for projects stored there. In Native mode, the Windows IDE delegates filesystem and process operations to the Rust-based IJent agent inside WSL, with EelApi abstracting local and remote environments for IDE and plugin code. Earlier approaches included 9P filesystem access, WSLg, and Remote Development, with problems involving symlink handling, latency, GUI limitations, installation overhead, and client–backend communication costs. Performance tests on a cold first open of spring-framework measured Native mode at 11.5 seconds to become ready versus 18.5 seconds for 9P, while project-tree scanning took 3.7 versus 8.1 seconds. Remote Development remains available, but direct project opening is now preferred in IntelliJ IDEA, WebStorm, and PhpStorm.

## Context

JetBrains needed to support IDE capabilities such as terminal use, running, debugging, profiling, indexing, and file operations against projects in WSL while keeping latency low enough for a quick, natural coding experience.

## Approach / What changed

Native mode keeps the IDE as a Windows application and uses the Rust-based IJent agent inside WSL for filesystem, process, and environment operations. EelApi provides an environment-agnostic interface for the IDE and plugins, while stdio and Hyper-V sockets provide transport options.

## Takeaways

- 9P access caused symlink-resolution problems, latency, degraded throughput, and delays from Microsoft Defender scans, especially for workflows involving many small files.
- IJent performs filesystem operations inside WSL, preserving Linux path and symbolic-link semantics while avoiding an additional Java or Kotlin runtime in WSL or containers.
- In the supplied benchmark, Native mode reduced time to readiness by 38% and project-tree scanning by 54% compared with 9P for a cold first open of spring-framework.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Performance](https://yomu.fyi/topic/performance), [Rust](https://yomu.fyi/topic/rust), [WSL](https://yomu.fyi/topic/wsl)

- Source: [Jetbrains](https://blog.jetbrains.com/platform/2026/09/the-evolution-of-wsl-support-in-jetbrains-ides)
- Source URL: https://blog.jetbrains.com/platform/2026/09/the-evolution-of-wsl-support-in-jetbrains-ides
- Ingested by Yomu: 2026-09-09T12:02:27.093Z

[Read original post](https://blog.jetbrains.com/platform/2026/09/the-evolution-of-wsl-support-in-jetbrains-ides)