0.102

0.102 is the largest devrig and MCP Steroid release yet — 535 pre-release commits touching both halves of the product. The headline: **devrig can now bootstrap a headless Remote Development backend entirely from an agent session**, completing the capability goals of the [product strategy](https://devrig.dev/docs/strategy/). Beyond that, **devrig** — the CLI you install and run — grows one unified command surface where every `steroid_*` MCP tool is a subcommand generated from its own schema, keeps itself up to date automatically, installs the MCP Steroid plugin into your running IDEs, and downloads 14 JetBrains IDE products. **The MCP Steroid plugin** compiles `steroid_execute_code` scripts roughly 3×–10× faster with an in-process Kotlin compiler, returns machine-parseable results, is ready for IntelliJ 2026.3 EAP, loads on Android Studio, and picked up a long list of correctness, modality, and Windows fixes.

> **`devrig` is the recommended entry point.** Direct use of the plugin's HTTP server is still supported (now explicitly marked deprecated in the settings UI), but `devrig` owns installation, the bundled Java runtime, agent registration, updates, and backend lifecycle.

> **One name, one home.** This release completes a transition: what started as *MCP Steroid* at `mcp-steroid.jonnyzzz.com` now lives at **[devrig.dev](https://devrig.dev)** — devrig is the product you install and run; MCP Steroid remains the name of the IDE plugin it talks to. The old host redirects permanently.

### Breaking changes

### Headless Remote Development backends — the strategy milestone

The essential change of 0.102: devrig can now launch a downloaded IDE as a **headless managed Remote Development backend** with MCP Steroid pre-provisioned — no desktop session, no attached client window. With it, the capability goals of the [product strategy](https://devrig.dev/docs/strategy/) are all in place: devrig runs in headless environments end to end, so the full IDE — inspections, refactorings, debugger, test runs — is available to **every agent wherever it executes**, not only next to a developer's open desktop IDE.

### One devrig CLI, generated from the tools' own schemas

Every `steroid_*` MCP tool is now a first-class devrig subcommand **auto-generated from its own schema metadata** — adding a tool adds its command, and the served stdio MCP surface registers from the same canonical spec list, so the CLI and the MCP server can never drift ([#284](https://github.com/jonnyzzz/mcp-steroid/issues/284), [#437](https://github.com/jonnyzzz/mcp-steroid/issues/437), [#356](https://github.com/jonnyzzz/mcp-steroid/issues/356)); a golden test pins the MCP wire unchanged.

### devrig keeps itself up to date

devrig now auto-updates ([#270](https://github.com/jonnyzzz/mcp-steroid/issues/270), [#380](https://github.com/jonnyzzz/mcp-steroid/issues/380)): when the published `version.json` promotes a newer version, running sessions download and run the official installer, coordinated across concurrent devrig processes via per-pid marker files — simple by design: **no lock files, no failure-count state**, lower-pid-wins races, a stdout-purity test guarding the MCP channel ([#373](https://github.com/jonnyzzz/mcp-steroid/issues/373), [#268](https://github.com/jonnyzzz/mcp-steroid/issues/268) closed by this design). Design story: [Install, Launch, Update: Shipping a CLI on Five Platforms — the devrig Approach](https://jonnyzzz.com/blog/2026/08/06/devrig-install-launch-autoupdate/).

### The Kotlin compiler update: in-process compilation, 3×–10× faster

The fixed per-call Kotlin compiler startup — **7.8 seconds, 94% of wall time** — is gone ([#207](https://github.com/jonnyzzz/mcp-steroid/issues/207)). Snippet compilation moved onto the [Kotlin Build Tools API (BTA)](https://github.com/JetBrains/kotlin/tree/master/compiler/build-tools/kotlin-build-tools-api) with one shared in-process build session per project ([#361](https://github.com/jonnyzzz/mcp-steroid/issues/361)): the Kotlin daemon machinery is gone, the plugin no longer downloads a kotlinc distribution at all (the compiler jars ship in the plugin, 12→10 jars), and pinning the compiler environment per session cuts warm compiles from 367 ms to 218 ms. BTA is the lever that makes this optimization possible.

**Yahor Berdnikau ([@Tapchicoma](https://github.com/Tapchicoma)) and the Kotlin team contributed this migration** — thank you, Yahor and team, for the collaboration and the support along the way.

### Ready for IntelliJ 2026.3 EAP and Android Studio

### `steroid_execute_code` output is machine-parseable again

For successful executions, the tool result is exactly the `execution_id:` header plus your script's printed output — stage framing and progress lines no longer interleave with the payload, so a script printing a single JSON document parses again ([#154](https://github.com/jonnyzzz/mcp-steroid/issues/154), [#159](https://github.com/jonnyzzz/mcp-steroid/issues/159)). Progress still flows to `idea.log`, MCP progress notifications, and the execution event log.

### The host IDE's identity is back in `list_projects` / `list_windows`

Both list tools carry a `backends[]` lookup resolving each entry's `backend_name` to the host IDE's identity ([#155](https://github.com/jonnyzzz/mcp-steroid/issues/155)) — a fresh IDE with zero open projects is identifiable with one cheap tool call:

```json

"backends": [

{ "backend_name": "iu-47qi79c1",

"intellij": { "name": "IntelliJ IDEA 2026.1.3", "version": "2026.1.3", "build": "IU-261.25134.95" } }

]

```

**Migration:** parsers reading the old top-level `ide.*` switch to `backends[0].intellij`. devrig's `project` / `backend` output carries the same identity keys in the same order.

### `steroid_execute_code` reliability and IDE responsiveness

### Execution history in one shared store — and we'd love to see yours

Execution history moved into **collision-safe shared storage under `~/.mcp-steroid/runs`** with full backend provenance ([#280](https://github.com/jonnyzzz/mcp-steroid/issues/280), [#433](https://github.com/jonnyzzz/mcp-steroid/issues/433), [#414](https://github.com/jonnyzzz/mcp-steroid/issues/414)); execution events route through a bounded serial write queue so log order is deterministic and a write failure fails the call honestly ([#436](https://github.com/jonnyzzz/mcp-steroid/issues/436)).

Sharing that folder shapes the product: **we are looking forward to your execution histories** — real `~/.mcp-steroid/runs` sessions are exactly what we analyze to adjust and fine-tune the tools, prompts, and recipes ([how the learning loop works](https://devrig.dev/docs/learning-methodology/), [what to send and how](https://devrig.dev/docs/need-your-experiments-and-support/)). **We also welcome proof-of-concept customers and enterprise partners** — to have devrig evaluated on your repositories with us, see [how you can help](https://devrig.dev/docs/strategy/) and get in touch.

### Fourteen downloadable IDE products, resolved reliably

PhpStorm, RubyMine, DataGrip, RustRover, and MPS join the catalog — **14 IDE products, up from nine** ([#430](https://github.com/jonnyzzz/mcp-steroid/issues/430), [#434](https://github.com/jonnyzzz/mcp-steroid/issues/434)).

### `devrig install`: agents, the plugin, and any MCP client

### In-IDE onboarding and a devrig-first settings page

When devrig is missing, the plugin can show a single promotion balloon linking devrig.dev — behind a registry key that is **off by default**; the settings page carries the same offer as the default surface ([#367](https://github.com/jonnyzzz/mcp-steroid/issues/367)). One click installs devrig through devrig's own updater machinery (shared per-pid markers prevent duplicate ~611 MB downloads), and installing devrig registers nothing with any agent.

The settings page is one **Devrig** section (**Tools → Devrig — MCP Steroid**, [#394](https://github.com/jonnyzzz/mcp-steroid/issues/394)) plus a collapsed direct-HTTP section marked deprecated: a copyable install one-liner next to a button that runs the same script, display-only `devrig install ` rows, and a collapsed stdio `mcpServers` snippet for other MCP clients. Every displayed path is the real absolute OS-native path. The Marketplace listing was rewritten around the core value ([#355](https://github.com/jonnyzzz/mcp-steroid/issues/355), [#395](https://github.com/jonnyzzz/mcp-steroid/issues/395)).

### devrig sessions that fail loudly, with bounded process waits

### Windows support, validated on real Windows

The devrig launcher, managed-backend commands, and the test infrastructure now work on Windows dev hosts ([#158](https://github.com/jonnyzzz/mcp-steroid/issues/158)); `:test-integration-agent-launch` runs the same agent-launch matrix on Windows and Linux with per-OS assertions ([#255](https://github.com/jonnyzzz/mcp-steroid/issues/255), [#257](https://github.com/jonnyzzz/mcp-steroid/issues/257), [#262](https://github.com/jonnyzzz/mcp-steroid/issues/262), [#269](https://github.com/jonnyzzz/mcp-steroid/issues/269)). The suites stay genuinely Windows-correct — CRLF-normalized assertions, `Path.of(...)`-built path fragments, an injectable executability probe ([#445](https://github.com/jonnyzzz/mcp-steroid/issues/445)) — and the agent CLI test runner bounds whole process trees and cleans up under NTFS lock semantics ([#407](https://github.com/jonnyzzz/mcp-steroid/issues/407)).

### Install scripts: correct next steps, session PATH, honest naming

The installer build and verification model — every URL and SHA-256 baked in at build time, per-platform JDKs, PGP-verified vendor feeds — is on the blog: [Install, Launch, Update: Shipping a CLI on Five Platforms — the devrig Approach](https://jonnyzzz.com/blog/2026/08/06/devrig-install-launch-autoupdate/).

### Prompt corpus: recipes that work on every IDE

### devrig.dev everywhere, and a devrig-first website

**https://devrig.dev is the single canonical public identity** ([#197](https://github.com/jonnyzzz/mcp-steroid/issues/197), [#319](https://github.com/jonnyzzz/mcp-steroid/issues/319), [#330](https://github.com/jonnyzzz/mcp-steroid/issues/330), [#335](https://github.com/jonnyzzz/mcp-steroid/issues/335)): loop-free redirects from the old host, corrected canonical/OG/sitemap metadata, protected by build-time assertions and post-deploy live checks ([#331](https://github.com/jonnyzzz/mcp-steroid/issues/331), [#332](https://github.com/jonnyzzz/mcp-steroid/issues/332)).

### Under the hood: build, CI, and shared internals

### Known issues

### Acknowledgements

0.102 is the first release of this project built by a real team — thank you to every contributor:

Full release notes: devrig.dev/releases/0.102/