pi-x-ide 1.13.0 → 1.14.0

package/README.md

@@ -2,7 +2,7 @@
 
 > Pi extension package for IDE selection context integration.
 
-Automatically attaches the currently opened or selected file and text range from VS Code, Zed, and Neovim to the Pi TUI, submitting them as conversation context to the LLM.
+Automatically attaches the currently opened or selected file and text range from VS Code, Zed, Neovim, and JetBrains IDEs to the Pi TUI, submitting them as conversation context to the LLM.
 
 ---
 
@@ -14,8 +14,6 @@ Automatically attaches the currently opened or selected file and text range from
 pi install npm:pi-x-ide
 ```
 
-This installs `pi-x-ide` as a global Pi extension. Pi loads it automatically on startup — no flags needed.
-
 ### Install the IDE Extension
 
 #### VS Code / Cursor / Windsurf
@@ -51,16 +49,22 @@ SHA-256 digest before caching it. If the download or checksum verification fails
 or no binary matches your platform, the plugin falls back to the bundled Node.js
 sidecar — Node.js is then required on PATH.
 
-The binary is cached under `stdpath("cache")/pi-x-ide/` and reused on subsequent
-starts. Plugin updates trigger a one-time re-download.
+Downloaded binaries are cached under `stdpath("cache")/pi-x-ide/` and reused on
+subsequent starts. The optional lazy.nvim build hook uses the bundled binary when
+present; otherwise it checks the release digest on install and update,
+downloading only when the cached binary is missing or stale.
 
 **lazy.nvim:**
 
 ```lua
 {
   "balaenis/pi-x-ide",
+  build = function(plugin)
+    vim.opt.rtp:prepend(plugin.dir .. "/ide-plugins/nvim")
+    require("pi_x_ide.download").run({ refresh = true })
+  end,
   init = function(plugin)
-    vim.opt.rtp:prepend(plugin.dir .. "/nvim")
+    vim.opt.rtp:prepend(plugin.dir .. "/ide-plugins/nvim")
   end,
   main = "pi_x_ide",
   opts = {
@@ -69,17 +73,46 @@ starts. Plugin updates trigger a one-time re-download.
 }
 ```
 
-> **Note:** The `init` block manually adds the `nvim/` subdirectory to the runtime path to avoid a Lua module resolution issue with some lazy.nvim versions. The plugin options are passed through lazy.nvim's recommended `opts` field.
+> **Note:** The `init` block manually adds the `ide-plugins/nvim/` subdirectory to the runtime path to avoid a Lua module resolution issue with some lazy.nvim versions. The plugin options are passed through lazy.nvim's recommended `opts` field.
+>
+> The optional `build` hook resolves the bundled sidecar binary when present;
+> otherwise it checks the GitHub Release asset digest at install/update time
+> (`:Lazy build pi-x-ide` to re-run) and downloads only when the cached binary is
+> missing or stale. It is safe to omit: the plugin still downloads the binary
+> lazily on first start and falls back to the Node.js sidecar if the download is
+> unavailable.
 
 **Native package:**
 
 ```vim
-set runtimepath+=/path/to/pi-x-ide/nvim
+set runtimepath+=/path/to/pi-x-ide/ide-plugins/nvim
 lua require("pi_x_ide").setup({ keymap = "<leader>pa" })
 ```
 
 See [Configuration Reference](#neovim-2) for full setup options, commands, and troubleshooting.
 
+#### JetBrains IDEs
+
+JetBrains support is provided by the plugin project under `ide-plugins/jetbrains`. The MVP is installed manually: build a local ZIP and install it through the IDE, or run it in a sandbox IDE for development.
+
+Run a sandbox IDE:
+
+```bash
+cd ide-plugins/jetbrains
+./gradlew runIde
+```
+
+Build a plugin ZIP for manual installation:
+
+```bash
+cd ide-plugins/jetbrains
+./gradlew buildPlugin
+```
+
+The ZIP is written to `ide-plugins/jetbrains/build/distributions/`. Install it from **Settings | Plugins | ⚙ | Install Plugin from Disk...**.
+
+JetBrains MVP support includes live active-file tracking, live selection tracking, `Ctrl+Alt+K` / **Pi x IDE: Attach Selection**, Pi-side `/ide auto`, and **Pi x IDE: Open Pi Terminal**. Diagnostic Quick Fix actions and Pi-side automatic JetBrains plugin installation are not part of the MVP.
+
 ### Connect Pi & Verify
 
 Start Pi in the **same project directory** as your IDE workspace:
@@ -88,7 +121,7 @@ Start Pi in the **same project directory** as your IDE workspace:
 pi
 ```
 
-Pi auto-loads `pi-x-ide` and connects to your IDE. The TUI should display `IDE: vscode ✓` in the footer and a widget showing the IDE name, workspace, current file, and selection range.
+Pi auto-loads `pi-x-ide` and connects to your IDE. The TUI should display a connected IDE source such as `IDE: vscode ✓` or `IDE: jetbrains ✓` in the footer and a widget showing the IDE name, workspace, current file, and selection range.
 
 **Verify it works:**
 
@@ -98,11 +131,11 @@ Open a file in your IDE and select some text. The widget should update in real t
 IDE: vscode ✓ src/foo.ts#L10-L20 pending
 ```
 
-Attach the selection from either side: press `Ctrl+Alt+K` (Linux/Windows) or `Cmd+Alt+K` (macOS) in a VS Code-family IDE, or focus the Pi TUI and press `Ctrl+Alt+K` / run `/ide attach`. The Pi input box should insert `@src/foo.ts#L10-L20`.
+Attach the selection from either side: press `Ctrl+Alt+K` (Linux/Windows) or `Cmd+Alt+K` (macOS) in a VS Code-family IDE, press `Ctrl+Alt+K` or run **Pi x IDE: Attach Selection** in JetBrains, use `:PiXIdeAttach` in Neovim, or focus the Pi TUI and press `Ctrl+Alt+K` / run `/ide attach`. The Pi input box should insert `@src/foo.ts#L10-L20`.
 
 Type a chat prompt in Pi and submit it. The selected text is injected as LLM context (does not persist in session history). After submission, the widget shows `sent`.
 
-For diagnostics in VS Code-family IDEs, connect Pi first, then place the cursor on an error or warning and open Quick Fix. The **Pi: Fix it** and **Pi: Send diagnostic** actions are shown only while at least one Pi client is connected. **Pi: Fix it** sends the diagnostic message, source range, nearby context lines, and related information to one connected Pi client and starts a diagnostic-analysis turn with a configurable prompt template (see [`fix_prompt`](#pi-side-configuration)). **Pi: Send diagnostic** sends the same context to one connected Pi client and pastes it into Pi's input box without starting a turn.
+For diagnostics in VS Code-family IDEs, connect Pi first, then place the cursor on an error or warning and open Quick Fix. The **Pi: Fix it** and **Pi: Send diagnostic** actions are shown only while at least one Pi client is connected. **Pi: Fix it** sends the diagnostic message, source range, nearby context lines, and related information to one connected Pi client and starts a diagnostic-analysis turn with a configurable prompt template (see [`fix_prompt`](#pi-side-configuration)). **Pi: Send diagnostic** sends the same context to one connected Pi client and pastes it into Pi's input box without starting a turn. JetBrains does not provide diagnostic Quick Fix actions in the MVP.
 
 **If the connection doesn't appear:**
 
@@ -110,6 +143,19 @@ For diagnostics in VS Code-family IDEs, connect Pi first, then place the cursor
 - If the IDE was started after Pi, reload the IDE window and run `/ide auto` again.
 - Run `/ide` to manually select a connection from the list.
 
+### WSL2 IDE Discovery
+
+VS Code Remote WSL works like a same-host setup: the extension host runs inside WSL, writes Linux-side lock files under `~/.pi/pi-x-ide/lock`, and binds the WebSocket server inside the WSL network namespace.
+
+When Pi runs inside WSL2 and a native Windows IDE plugin is running on the Windows side, Pi also scans Windows user lock directories such as `/mnt/c/Users/<user>/.pi/pi-x-ide/lock`. New Windows-side lock files include `runningInWindows: true`; Pi uses that metadata to try the WSL default gateway before falling back to the lock file's `host` value. Windows and WSL UNC paths are normalized before workspace matching and before formatting `@file#Lx-Ly` mentions.
+
+If your WSL networking mode, firewall, or endpoint security blocks the default gateway, set `PI_X_IDE_HOST_OVERRIDE`:
+
+```bash
+PI_X_IDE_HOST_OVERRIDE=127.0.0.1 pi
+PI_X_IDE_HOST_OVERRIDE=<windows-host-ip> pi
+```
+
 ### `/ide` Command Reference
 
 | Command        | Behavior                                                          |
@@ -181,6 +227,7 @@ Pi-side variables can be set as real environment variables or in `~/.pi/pi-x-ide
 | ------------------------------- | ------------- | ----------------------------------------------------------------------------------- |
 | `PI_X_IDE_AUTO_INSTALL`         | `1`           | Auto-install VS Code extension on Pi startup                                        |
 | `PI_X_IDE_ATTACH_SHORTCUT`      | `ctrl+alt+k`  | Pi TUI shortcut for `/ide attach`; set to `off`, `none`, `false`, or `0` to disable |
+| `PI_X_IDE_HOST_OVERRIDE`        | (unset)       | Override the host Pi uses for IDE WebSocket lock files; useful for WSL2 networking  |
 | `PI_X_IDE_ZED_DB`               | (auto-detect) | Override path to Zed SQLite database                                                |
 | `PI_X_IDE_ZED_POLL_INTERVAL_MS` | `1000`        | Zed SQLite polling interval, clamped to 100-2000 ms                                 |
 
@@ -194,14 +241,16 @@ See [schemas/config.json](schemas/config.json) for editor schema guidance. A [co
 
 ### Feature Parity
 
-| Feature                                              | VS Code                 | Zed        | Neovim                        |
-| ---------------------------------------------------- | ----------------------- | ---------- | ----------------------------- |
-| Live file tracking                                   | ✅ Real-time push       | ✅ polling | ✅ Real-time push via sidecar |
-| Live selection tracking                              | ✅ Real-time push       | ✅ polling | ✅ Real-time push via sidecar |
-| IDE context attach shortcut                          | ✅ Default `Ctrl+Alt+K` | ❌         | ✅ Custom configured keymap   |
-| Pi TUI context attach shortcut(default `Ctrl+Alt+K`) | ✅                      | ✅         | ✅                            |
-| LLM context injection                                | ✅                      | ✅         | ✅                            |
-| `/ide auto`                                          | ✅                      | ✅         | ✅                            |
+| Feature                                              | VS Code                 | Zed        | Neovim                        | JetBrains               |
+| ---------------------------------------------------- | ----------------------- | ---------- | ----------------------------- | ----------------------- |
+| Live file tracking                                   | ✅ Real-time push       | ✅ polling | ✅ Real-time push via sidecar | ✅ Real-time push       |
+| Live selection tracking                              | ✅ Real-time push       | ✅ polling | ✅ Real-time push via sidecar | ✅ Real-time push       |
+| IDE context attach shortcut                          | ✅ Default `Ctrl+Alt+K` | ❌         | ✅ Custom configured keymap   | ✅ Default `Ctrl+Alt+K` |
+| Pi TUI context attach shortcut(default `Ctrl+Alt+K`) | ✅                      | ✅         | ✅                            | ✅                      |
+| LLM context injection                                | ✅                      | ✅         | ✅                            | ✅                      |
+| `/ide auto`                                          | ✅                      | ✅         | ✅                            | ✅                      |
+| Diagnostic Quick Fix                                 | ✅                      | ❌         | ❌                            | ❌                      |
+| Auto-install                                         | ✅ VS Code-family only  | N/A        | ❌                            | ❌                      |
 
 ### Lock File Protocol
 
@@ -221,6 +270,7 @@ See [docs/specs/ide-protocol.md](docs/specs/ide-protocol.md) for protocol detail
 - bun ≥ 1.3 (`packageManager` declared as `bun@1.3.14`)
 - VS Code ≥ 1.120.0 (VS Code extension only)
 - Neovim ≥ 0.9 (Neovim plugin only)
+- JDK 21 (JetBrains plugin only; Gradle can download the toolchain automatically)
 
 ### Install & Build
 
@@ -229,8 +279,8 @@ Clone the repository, then build:
 ```bash
 git clone https://github.com/balaenis/pi-x-ide.git
 cd pi-x-ide
-bun install
-bun run build
+mise run setup
+mise run build
 ```
 
 To load the local build without installing globally:
@@ -239,15 +289,18 @@ To load the local build without installing globally:
 pi -e ./src/pi/index.ts
 ```
 
-All `bun run` commands have equivalent `mise run` tasks (see `mise.toml`):
+All build and check commands are defined as `mise run` tasks (see `.mise/tasks/`):
 
-| Command                       | Description                                                                                        |
-| ----------------------------- | -------------------------------------------------------------------------------------------------- |
-| `bun run build`               | Build Pi-side TypeScript → `dist/` + Neovim sidecar → `nvim/bin/` + VS Code bundle → `vscode/out/` |
-| `bun run typecheck`           | Type-check only (no output files)                                                                  |
-| `bun run test`                | Build + run unit tests                                                                             |
-| `bun run package:vsix`        | Package VS Code extension as VSIX                                                                  |
-| `bun run check:config-schema` | Verify `schemas/config.json` is in sync with the config registry                                   |
+| Command                        | Description                                                                                                                |
+| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------- |
+| `mise run build`               | Build Pi-side TypeScript → `dist/` + Neovim sidecar → `ide-plugins/nvim/bin/` + VS Code bundle → `ide-plugins/vscode/out/` |
+| `mise run typecheck`           | Type-check only (no output files)                                                                                          |
+| `mise run test`                | Build + run unit tests                                                                                                     |
+| `mise run package:vsix`        | Package VS Code extension as VSIX                                                                                          |
+| `mise run compile:jetbrains`   | Compile and test the JetBrains plugin with Gradle                                                                          |
+| `mise run package:jetbrains`   | Package the JetBrains plugin ZIP under `ide-plugins/jetbrains/build/distributions/`                                        |
+| `mise run verify:jetbrains`    | Run IntelliJ Plugin Verifier for the configured target IDE                                                                 |
+| `mise run check:config-schema` | Verify `schemas/config.json` is in sync with the config registry                                                           |
 
 ### Testing the VS Code Extension Locally
 
@@ -257,14 +310,14 @@ All `bun run` commands have equivalent `mise run` tasks (see `mise.toml`):
 2. Go to the **Run and Debug** panel (`Ctrl+Shift+D`).
 3. Select **Run Pi x IDE VS Code Extension**.
 4. Press **F5**:
-   - The `preLaunchTask` automatically runs `bun run build`.
+   - The `preLaunchTask` automatically runs `mise run build`.
    - A new VS Code window titled `[Extension Development Host]` opens.
 
 #### Option 2: Package VSIX and Install
 
 ```bash
-bun run package:vsix
-cd vscode && code --install-extension dist/pi-x-ide-$(node -p "require('./package.json').version").vsix
+mise run package:vsix
+cd ide-plugins/vscode && code --install-extension dist/pi-x-ide-$(node -p "require('./package.json').version").vsix
 ```
 
 The extension installed this way runs in all VS Code windows, independent of the F5 Extension Host.
@@ -277,6 +330,23 @@ ls -l ~/.pi/pi-x-ide/lock
 
 You should see a file like `vscode-12345-48123.lock`. If not, run **Developer: Reload Window** in VS Code.
 
+### Testing the JetBrains Plugin Locally
+
+Run a sandbox IDE:
+
+```bash
+cd ide-plugins/jetbrains
+./gradlew runIde
+```
+
+Build the installable plugin ZIP:
+
+```bash
+mise run package:jetbrains
+```
+
+The ZIP is written under `ide-plugins/jetbrains/build/distributions/`. For a smoke test, open this repository in the sandbox IDE, start `pi` from the same directory, open and select text in a local file, then press `Ctrl+Alt+K` or run **Pi x IDE: Attach Selection**. Pi should receive an `@relative/path#Lx-Ly` mention.
+
 ### Release
 
 This project uses [Release Please](https://github.com/googleapis/release-please) with [Conventional Commits](https://www.conventionalcommits.org/) to automate versioning and publishing.

package/README.zh-CN.md

@@ -2,7 +2,7 @@
 
 > 用于 IDE 选择上下文集成的 Pi 扩展包。
 
-自动将 VS Code、Zed 和 Neovim 中当前打开或选中的文件与文本范围附加到 Pi TUI，并作为对话上下文提交给 LLM。
+自动将 VS Code、Zed、Neovim 和 JetBrains IDE 中当前打开或选中的文件与文本范围附加到 Pi TUI，并作为对话上下文提交给 LLM。
 
 ---
 
@@ -14,8 +14,6 @@
 pi install npm:pi-x-ide
 ```
 
-将 `pi-x-ide` 安装为全局 Pi 扩展，Pi 启动时自动加载，无需额外参数。
-
 ### 安装 IDE 扩展
 
 #### VS Code / Cursor / Windsurf
@@ -50,16 +48,20 @@ x64 或 arm64），并在写入缓存前用 release asset 的 SHA-256 digest 做
 或校验失败、或无匹配二进制时，插件降级到内置的 Node.js sidecar — 此时需要
 PATH 中有 Node.js。
 
-二进制文件缓存在 `stdpath("cache")/pi-x-ide/` 目录，后续启动直接复用。插件
-更新后会触发一次重新下载。
+下载的二进制文件缓存在 `stdpath("cache")/pi-x-ide/` 目录，后续启动直接复用。可选的
+lazy.nvim build 钩子会优先使用插件包内的 bundled binary；如果不存在，则在安装和更新时检查 release digest，仅在缓存二进制缺失或过期时下载。
 
 **lazy.nvim：**
 
 ```lua
 {
   "balaenis/pi-x-ide",
+  build = function(plugin)
+    vim.opt.rtp:prepend(plugin.dir .. "/ide-plugins/nvim")
+    require("pi_x_ide.download").run({ refresh = true })
+  end,
   init = function(plugin)
-    vim.opt.rtp:prepend(plugin.dir .. "/nvim")
+    vim.opt.rtp:prepend(plugin.dir .. "/ide-plugins/nvim")
   end,
   main = "pi_x_ide",
   opts = {
@@ -68,17 +70,41 @@ PATH 中有 Node.js。
 }
 ```
 
-> **注意：** `init` 块手动将 `nvim/` 子目录加入 runtime path，以规避部分版本 lazy.nvim 的 Lua 模块解析兼容性问题。插件选项通过 lazy.nvim 推荐的 `opts` 字段传入。
+> **注意：** `init` 块手动将 `ide-plugins/nvim/` 子目录加入 runtime path，以规避部分版本 lazy.nvim 的 Lua 模块解析兼容性问题。插件选项通过 lazy.nvim 推荐的 `opts` 字段传入。
+>
+> 可选的 `build` 钩子会优先使用插件包内的 bundled sidecar 二进制；如果不存在，则在安装/更新时检查 GitHub Release asset digest（用 `:Lazy build pi-x-ide` 可重新触发），仅在缓存二进制缺失或过期时下载。该钩子可以省略：插件仍会在首次启动时按需下载二进制，下载不可用时回退到 Node.js sidecar。
 
 **原生 package：**
 
 ```vim
-set runtimepath+=/path/to/pi-x-ide/nvim
+set runtimepath+=/path/to/pi-x-ide/ide-plugins/nvim
 lua require("pi_x_ide").setup({ keymap = "<leader>pa" })
 ```
 
 完整配置选项、命令和故障排查见 [配置参考](#neovim-2)。
 
+#### JetBrains IDE
+
+JetBrains 支持由 `ide-plugins/jetbrains` 下的插件项目提供。MVP 需要手动安装：可以构建本地 ZIP 后从 IDE 安装，也可以在开发用 sandbox IDE 中运行。
+
+运行 sandbox IDE：
+
+```bash
+cd ide-plugins/jetbrains
+./gradlew runIde
+```
+
+构建用于手动安装的插件 ZIP：
+
+```bash
+cd ide-plugins/jetbrains
+./gradlew buildPlugin
+```
+
+ZIP 会输出到 `ide-plugins/jetbrains/build/distributions/`。在 JetBrains IDE 中通过 **Settings | Plugins | ⚙ | Install Plugin from Disk...** 安装。
+
+JetBrains MVP 支持实时活跃文件追踪、实时选区追踪、`Ctrl+Alt+K` / **Pi x IDE: Attach Selection**、Pi 侧 `/ide auto`，以及 **Pi x IDE: Open Pi Terminal**。诊断 Quick Fix 和 Pi 侧自动安装 JetBrains 插件不属于 MVP 范围。
+
 ### 连接 Pi 并验证
 
 在 IDE workspace **同一项目目录** 启动 Pi：
@@ -87,7 +113,7 @@ lua require("pi_x_ide").setup({ keymap = "<leader>pa" })
 pi
 ```
 
-Pi 自动加载 `pi-x-ide` 并连接 IDE。TUI 底部应显示 `IDE: vscode ✓`，输入框下方 widget 显示 IDE 名称、workspace、当前文件和选区范围。
+Pi 自动加载 `pi-x-ide` 并连接 IDE。TUI 底部应显示类似 `IDE: vscode ✓` 或 `IDE: jetbrains ✓` 的已连接 IDE source，输入框下方 widget 显示 IDE 名称、workspace、当前文件和选区范围。
 
 **验证是否正常：**
 
@@ -97,11 +123,11 @@ Pi 自动加载 `pi-x-ide` 并连接 IDE。TUI 底部应显示 `IDE: vscode ✓`
 IDE: vscode ✓ src/foo.ts#L10-L20 pending
 ```
 
-可以从任一侧附加选区：在 VS Code 系列 IDE 中按 `Ctrl+Alt+K`（Linux/Windows）或 `Cmd+Alt+K`（macOS），或聚焦 Pi TUI 后按 `Ctrl+Alt+K` / 运行 `/ide attach`。Pi 输入框应插入 `@src/foo.ts#L10-L20`。
+可以从任一侧附加选区：在 VS Code 系列 IDE 中按 `Ctrl+Alt+K`（Linux/Windows）或 `Cmd+Alt+K`（macOS），在 JetBrains 中按 `Ctrl+Alt+K` 或运行 **Pi x IDE: Attach Selection**，在 Neovim 中使用 `:PiXIdeAttach`，或聚焦 Pi TUI 后按 `Ctrl+Alt+K` / 运行 `/ide attach`。Pi 输入框应插入 `@src/foo.ts#L10-L20`。
 
 在 Pi 中输入对话提示并提交，选中文本会作为 LLM 上下文注入（不写入 session 历史）。提交后 widget 显示 `sent`。
 
-对于 VS Code 系列 IDE 中的诊断信息，先连接 Pi，再把光标放在 error 或 warning 上并打开 Quick Fix。只有至少一个 Pi 客户端已连接时，才会显示 **Pi: Fix it** 和 **Pi: Send diagnostic**。**Pi: Fix it** 会把诊断消息、源码范围、附近上下文行和 related information 发送给一个已连接的 Pi 客户端，并用可自定义的 prompt 模板自动开始诊断分析（参见 [`fix_prompt`](#pi-侧配置)）。**Pi: Send diagnostic** 会把相同上下文发送给一个已连接的 Pi 客户端并粘贴到 Pi 输入框，不会自动开始一轮对话。
+对于 VS Code 系列 IDE 中的诊断信息，先连接 Pi，再把光标放在 error 或 warning 上并打开 Quick Fix。只有至少一个 Pi 客户端已连接时，才会显示 **Pi: Fix it** 和 **Pi: Send diagnostic**。**Pi: Fix it** 会把诊断消息、源码范围、附近上下文行和 related information 发送给一个已连接的 Pi 客户端，并用可自定义的 prompt 模板自动开始诊断分析（参见 [`fix_prompt`](#pi-侧配置)）。**Pi: Send diagnostic** 会把相同上下文发送给一个已连接的 Pi 客户端并粘贴到 Pi 输入框，不会自动开始一轮对话。JetBrains MVP 不提供诊断 Quick Fix。
 
 **如果连接未出现：**
 
@@ -109,6 +135,19 @@ IDE: vscode ✓ src/foo.ts#L10-L20 pending
 - 如果 IDE 在 Pi 之后启动，reload IDE 窗口后再次运行 `/ide auto`
 - 运行 `/ide` 手动从列表中选择连接
 
+### WSL2 IDE 发现
+
+VS Code Remote WSL 的行为等同于同主机连接：扩展宿主运行在 WSL 内部，在 Linux 侧的 `~/.pi/pi-x-ide/lock` 写入 lock file，并在 WSL 网络命名空间中绑定 WebSocket server。
+
+当 Pi 运行在 WSL2 中，而原生 Windows IDE 插件运行在 Windows 侧时，Pi 也会扫描 Windows 用户 lock 目录，例如 `/mnt/c/Users/<user>/.pi/pi-x-ide/lock`。新的 Windows 侧 lock file 会包含 `runningInWindows: true`；Pi 会使用该元数据优先尝试 WSL 默认网关，再回退到 lock file 中的 `host`。Windows 路径和 WSL UNC 路径会在 workspace 匹配以及格式化 `@file#Lx-Ly` mention 前规范化。
+
+如果你的 WSL 网络模式、防火墙或终端安全策略阻止默认网关访问，可设置 `PI_X_IDE_HOST_OVERRIDE`：
+
+```bash
+PI_X_IDE_HOST_OVERRIDE=127.0.0.1 pi
+PI_X_IDE_HOST_OVERRIDE=<windows-host-ip> pi
+```
+
 ### `/ide` 命令参考
 
 | 命令           | 行为                                              |
@@ -179,6 +218,7 @@ Pi 侧变量可设为真实环境变量或写入 `~/.pi/pi-x-ide/config.json`
 | ------------------------------- | ------------ | ------------------------------------------------------------------------- |
 | `PI_X_IDE_AUTO_INSTALL`         | `1`          | Pi 启动时自动安装 VS Code 扩展                                            |
 | `PI_X_IDE_ATTACH_SHORTCUT`      | `ctrl+alt+k` | Pi TUI 的 `/ide attach` 快捷键；设为 `off`、`none`、`false` 或 `0` 可禁用 |
+| `PI_X_IDE_HOST_OVERRIDE`        | （未设置）   | 覆盖 Pi 连接 IDE WebSocket lock file 时使用的 host；适用于 WSL2 网络场景  |
 | `PI_X_IDE_ZED_DB`               | （自动检测） | 覆盖 Zed SQLite 数据库路径                                                |
 | `PI_X_IDE_ZED_POLL_INTERVAL_MS` | `1000`       | Zed SQLite 轮询间隔，会被限制在 100-2000 ms 范围                          |
 
@@ -192,14 +232,16 @@ Pi 侧变量可设为真实环境变量或写入 `~/.pi/pi-x-ide/config.json`
 
 ### 功能对比
 
-| 功能                                             | VS Code              | Zed         | Neovim                   |
-| ------------------------------------------------ | -------------------- | ----------- | ------------------------ |
-| 实时文件追踪                                     | ✅ 实时推送          | ✅ 1 秒轮询 | ✅ 通过 sidecar 实时推送 |
-| 实时选区追踪                                     | ✅ 实时推送          | ✅ 1 秒轮询 | ✅ 通过 sidecar 实时推送 |
-| IDE 上下文 attach 快捷键                         | ✅ 默认 `Ctrl+Alt+K` | ❌          | ✅ 自定义快捷键 keymap   |
-| Pi TUI 上下文 attach 快捷键（默认 `Ctrl+Alt+K`） | ✅                   | ✅          | ✅                       |
-| LLM 上下文注入                                   | ✅                   | ✅          | ✅                       |
-| `/ide auto`                                      | ✅                   | ✅          | ✅                       |
+| 功能                                             | VS Code              | Zed         | Neovim                   | JetBrains            |
+| ------------------------------------------------ | -------------------- | ----------- | ------------------------ | -------------------- |
+| 实时文件追踪                                     | ✅ 实时推送          | ✅ 1 秒轮询 | ✅ 通过 sidecar 实时推送 | ✅ 实时推送          |
+| 实时选区追踪                                     | ✅ 实时推送          | ✅ 1 秒轮询 | ✅ 通过 sidecar 实时推送 | ✅ 实时推送          |
+| IDE 上下文 attach 快捷键                         | ✅ 默认 `Ctrl+Alt+K` | ❌          | ✅ 自定义快捷键 keymap   | ✅ 默认 `Ctrl+Alt+K` |
+| Pi TUI 上下文 attach 快捷键（默认 `Ctrl+Alt+K`） | ✅                   | ✅          | ✅                       | ✅                   |
+| LLM 上下文注入                                   | ✅                   | ✅          | ✅                       | ✅                   |
+| `/ide auto`                                      | ✅                   | ✅          | ✅                       | ✅                   |
+| 诊断 Quick Fix                                   | ✅                   | ❌          | ❌                       | ❌                   |
+| 自动安装                                         | ✅ 仅 VS Code 系列   | N/A         | ❌                       | ❌                   |
 
 ### Lock File 协议
 
@@ -219,6 +261,7 @@ Pi 通过 `ctx.cwd` 与 lock file 中的 `workspaceFolders` 做最长路径匹
 - bun ≥ 1.3（`packageManager` 声明为 `bun@1.3.14`）
 - VS Code ≥ 1.120.0（仅 VS Code 扩展需要）
 - Neovim ≥ 0.9（仅 Neovim 插件需要）
+- JDK 21（仅 JetBrains 插件需要；Gradle 可自动下载 toolchain）
 
 ### 安装与构建
 
@@ -227,8 +270,8 @@ Clone 仓库后构建：
 ```bash
 git clone https://github.com/balaenis/pi-x-ide.git
 cd pi-x-ide
-bun install
-bun run build
+mise run setup
+mise run build
 ```
 
 加载本地构建（无需全局安装）：
@@ -237,15 +280,18 @@ bun run build
 pi -e ./src/pi/index.ts
 ```
 
-所有 `bun run` 命令都有等效的 `mise run` 任务（见 `mise.toml`）：
+所有构建与检查命令都定义为 `mise run` 任务（见 `.mise/tasks/`）：
 
-| 命令                          | 说明                                                                                            |
-| ----------------------------- | ----------------------------------------------------------------------------------------------- |
-| `bun run build`               | 编译 Pi 侧 TypeScript → `dist/` + Neovim sidecar → `nvim/bin/` + VS Code bundle → `vscode/out/` |
-| `bun run typecheck`           | 类型检查（不产出文件）                                                                          |
-| `bun run test`                | 编译 + 运行单元测试                                                                             |
-| `bun run package:vsix`        | 打包 VS Code 扩展为 VSIX                                                                        |
-| `bun run check:config-schema` | 验证 `schemas/config.json` 与配置注册表是否同步                                                 |
+| 命令                           | 说明                                                                                                                    |
+| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
+| `mise run build`               | 编译 Pi 侧 TypeScript → `dist/` + Neovim sidecar → `ide-plugins/nvim/bin/` + VS Code bundle → `ide-plugins/vscode/out/` |
+| `mise run typecheck`           | 类型检查（不产出文件）                                                                                                  |
+| `mise run test`                | 编译 + 运行单元测试                                                                                                     |
+| `mise run package:vsix`        | 打包 VS Code 扩展为 VSIX                                                                                                |
+| `mise run compile:jetbrains`   | 用 Gradle 编译并测试 JetBrains 插件                                                                                     |
+| `mise run package:jetbrains`   | 将 JetBrains 插件打包为 `ide-plugins/jetbrains/build/distributions/` 下的 ZIP                                           |
+| `mise run verify:jetbrains`    | 对配置的目标 IDE 运行 IntelliJ Plugin Verifier                                                                          |
+| `mise run check:config-schema` | 验证 `schemas/config.json` 与配置注册表是否同步                                                                         |
 
 ### 本地测试 VS Code 扩展
 
@@ -255,14 +301,14 @@ pi -e ./src/pi/index.ts
 2. 进入 **Run and Debug** 面板（`Ctrl+Shift+D`）。
 3. 选择 **Run Pi x IDE VS Code Extension**。
 4. 按 **F5**：
-   - preLaunchTask 会自动执行 `bun run build`。
+   - preLaunchTask 会自动执行 `mise run build`。
    - 打开一个标题包含 `[Extension Development Host]` 的新 VS Code 窗口。
 
 #### 方式二：打包 VSIX 后安装
 
 ```bash
-bun run package:vsix
-cd vscode && code --install-extension dist/pi-x-ide-$(node -p "require('./package.json').version").vsix
+mise run package:vsix
+cd ide-plugins/vscode && code --install-extension dist/pi-x-ide-$(node -p "require('./package.json').version").vsix
 ```
 
 这样安装的扩展在所有 VS Code 窗口中运行，不依赖 F5 Extension Host。
@@ -275,6 +321,23 @@ ls -l ~/.pi/pi-x-ide/lock
 
 应看到类似 `vscode-12345-48123.lock` 的文件。如果没有，在 VS Code 中执行 **Developer: Reload Window**。
 
+### 本地测试 JetBrains 插件
+
+运行 sandbox IDE：
+
+```bash
+cd ide-plugins/jetbrains
+./gradlew runIde
+```
+
+构建可安装的插件 ZIP：
+
+```bash
+mise run package:jetbrains
+```
+
+ZIP 会输出到 `ide-plugins/jetbrains/build/distributions/`。Smoke test：在 sandbox IDE 中打开本仓库，从同一目录启动 `pi`，打开并选择一个本地文件中的文本，然后按 `Ctrl+Alt+K` 或运行 **Pi x IDE: Attach Selection**。Pi 应收到 `@relative/path#Lx-Ly` mention。
+
 ### 发布
 
 本项目使用 [Release Please](https://github.com/googleapis/release-please) 和 [Conventional Commits](https://www.conventionalcommits.org/) 来自动化版本管理和发布流程。

package/dist/package.json

@@ -1,6 +1,6 @@
 {
     "name": "pi-x-ide",
-    "version": "1.13.0",
+    "version": "1.14.0",
     "description": "Pi extension package for IDE selection context integration.",
     "files": [
         "dist",
@@ -14,7 +14,10 @@
         "vscode",
         "zed",
         "neovim",
-        "nvim"
+        "nvim",
+        "jetbrains",
+        "intellij",
+        "idea"
     ],
     "license": "Apache-2.0",
     "repository": {
@@ -26,7 +29,7 @@
     },
     "homepage": "https://github.com/balaenis/pi-x-ide#readme",
     "workspaces": [
-        "vscode"
+        "ide-plugins/vscode"
     ],
     "packageManager": "bun@1.3.14",
     "engines": {
@@ -34,24 +37,6 @@
     },
     "type": "commonjs",
     "main": "./dist/src/pi/index.js",
-    "scripts": {
-        "typecheck": "tsc -p tsconfig.json --noEmit && bun run --filter './vscode' typecheck",
-        "generate:config-schema": "bun run scripts/generate-config-schema.cjs",
-        "check:config-schema": "bun run scripts/generate-config-schema.cjs --check",
-        "test": "bun run check:config-schema && bun run compile && node --test dist/test/*.test.js",
-        "lint": "eslint .",
-        "lint:fix": "eslint . --fix",
-        "format": "prettier --write .",
-        "format:check": "prettier --check .",
-        "compile": "tsc -p tsconfig.json",
-        "compile:vsix": "bun run --filter './vscode' compile",
-        "sync:vsix-assets": "bun run --filter './vscode' sync:assets",
-        "package:vsix": "bun run --filter './vscode' package",
-        "package:nvim-sidecar": "bun run scripts/build-nvim-sidecar.mjs --production",
-        "package:nvim-sidecar:all": "bun run scripts/build-nvim-sidecar.mjs --production --target=all",
-        "build": "bun run compile && bun run compile:vsix && bun run package:nvim-sidecar",
-        "build:all": "bun run compile && bun run compile:vsix && bun run package:nvim-sidecar:all"
-    },
     "dependencies": {
         "ws": "^8.21.0"
     },

package/dist/src/pi/connection.d.ts

@@ -2,7 +2,8 @@ import { type DiagnosticFixRequestedParams, type AtMentionedParams, type EditorS
 export declare const IDE_CONNECT_TIMEOUT_MS = 5000;
 export declare class IdeConnectionTimeoutError extends Error {
     readonly candidate: LockFileCandidate;
-    constructor(candidate: LockFileCandidate);
+    readonly host: string;
+    constructor(candidate: LockFileCandidate, host?: string);
 }
 export interface IdeConnectionCallbacks {
     onConnected?: (server: {
@@ -17,14 +18,19 @@ export interface IdeConnectionCallbacks {
     onDiagnosticFixRequested?: (params: DiagnosticFixRequestedParams) => void;
     onError?: (error: Error) => void;
 }
+export interface IdeConnectionOptions {
+    resolveHost?: (lock: LockFileCandidate["lock"]) => Promise<string>;
+    env?: NodeJS.ProcessEnv;
+}
 export declare class IdeConnection {
     readonly candidate: LockFileCandidate;
     private readonly cwd;
     private readonly callbacks;
+    private readonly options;
     private socket?;
     private nextId;
     private closedByUser;
-    constructor(candidate: LockFileCandidate, cwd: string, callbacks: IdeConnectionCallbacks);
+    constructor(candidate: LockFileCandidate, cwd: string, callbacks: IdeConnectionCallbacks, options?: IdeConnectionOptions);
     get isOpen(): boolean;
     connect(timeoutMs?: number): Promise<void>;
     disconnect(): void;