---
ai-generated: true
created: 2026-05-05
version: 0.94.0
---

# 0.94.0 Release Social Posts

## LinkedIn Post

IntelliJ for AI Agents, not humans -- MCP Steroid v0.94.0 is out.

What's new:

1. New tool: `steroid_apply_patch`. Atomic multi-file batch edits in a single MCP call. Pre-flight rejects ambiguous matches before touching any document; all hunks land in one undoable command; touched documents are saved before the response returns. In our DPAIA Microshop benchmark, Claude Code rewrote 8 hunks across 8 files in 66 ms — zero native Edit fallbacks.

2. Periodic DialogKiller replaces the old ModalityStateMonitor. 236 lines of misclassification logic gone. Maven and Gradle test runs no longer get cancelled mid-flight, SDK-lookup banners stop being flagged as modals, and `steroid_execute_code` gets a per-call `dialog_killer` switch.

3. Two new MCP resources for the most painful flows: `mcp-steroid://skill/execute-code-gradle` and a rewritten `mcp-steroid://skill/execute-code-maven` — both pinned to the IDE-native test execution path. The `mcp-steroid://lsp/rename` recipe is now a semantic rename via IntelliJ's RenameProcessor instead of regex.

4. ~10× faster no-change TDD loop, contributed by Dmitry Protsenko (@NordCoderd). Four orthogonal sources of cache invalidation in the build, all traced and fixed in one PR. `./gradlew :ij-plugin:test` drops from ~28 s to ~3 s.

5. Plugin Verifier reports zero internal-API usages on both IntelliJ 2025.3 and 2026.1. Forward compatibility holds.

The evals repo is open: github.com/jonnyzzz/mcp-steroid. 87+ prompt resources, Docker integration tests for Claude, Codex, and Gemini, DPAIA arena benchmarks. Contribute a scenario, run the evals, improve a skill.

Release notes: https://mcp-steroid.jonnyzzz.com/releases/0.94.0/
Strategy: https://mcp-steroid.jonnyzzz.com/docs/strategy/
Skill factory: https://jonnyzzz.com/blog/2026/04/08/mcp-steroid-skill-factory/

#MCPSteroid #IntelliJ #AgenticCoding #MCP #AIAgents #JetBrains #OpenSource #AndroidStudio #Codex #Claude

---

## X (Twitter) Post — Thread (3 tweets)

**Tweet 1:**
IntelliJ for AI Agents, not humans — MCP Steroid v0.94.0.

New `steroid_apply_patch` tool: atomic multi-file batch edits in one MCP call. Claude rewrote 8 hunks across 8 files in 66 ms in our Microshop benchmark.

🔗 https://mcp-steroid.jonnyzzz.com/releases/0.94.0/

**Tweet 2:**
Also in this release:
— DialogKiller replaces ModalityStateMonitor (236 lines of misclassification gone)
— New Gradle + Maven prompt resources, IDE-native test path
— Semantic LSP rename via RenameProcessor (not regex)
— Zero internal-API usages on 2025.3 and 2026.1

**Tweet 3:**
Bonus from a community PR by @NordCoderd: ~10× faster no-change TDD loop. Four orthogonal sources of cache invalidation in the build, traced and fixed in one go.

Contribute a scenario, run the evals, improve a skill:
github.com/jonnyzzz/mcp-steroid

#MCPSteroid #AgenticAI #IntelliJ #MCP #OpenSource

---

## X (Twitter) Post — Single tweet variant

IntelliJ for AI Agents, not humans — MCP Steroid v0.94.0.

New `steroid_apply_patch`: atomic multi-file edits, 8 hunks × 8 files in 66 ms. DialogKiller replaces ModalityStateMonitor. Zero internal-API usages on 2025.3 and 2026.1.

Contribute: github.com/jonnyzzz/mcp-steroid

---

## Notes for Eugene

- The "8 hunks × 8 files in 66 ms" data point is the strongest hook — it's a concrete, measured contrast against one-edit-per-tool-call. Lead with it.
- Credit @NordCoderd by handle in the LinkedIn post and the X thread — the ~10× TDD speedup is a real community win and reinforces the open-collaboration angle from 0.93.0.
- "Zero internal-API usages" carries forward the 0.93.0 narrative arc (29 → 4 → 0). Keeps the forward-compatibility story alive.
- Avoid naming specific agent model versions; they date quickly.
- The LinkedIn post is ~250 words — slightly above 0.93.0 because we have more concrete numbers worth quoting; trim point 4 (TDD) if you need to fit pre-fold on desktop.
- The single-tweet variant intentionally drops the "DialogKiller" name (jargony for non-IntelliJ-developer audiences) and keeps the apply_patch + verifier numbers.
