RunVSAgent
Run selected VS Code coding agents and extensions inside JetBrains IDEs.
What does this agent do, and when should you use it?
RunVSAgent is a cross-IDE integration tool for running VS Code-based coding agents and extensions in JetBrains products such as IntelliJ IDEA, WebStorm, and PyCharm. Its architecture combines a Kotlin JetBrains Plugin with a Node.js Extension Host, communicating through RPC over Unix Domain Sockets or Named Pipes. The Extension Host supplies a VSCode API Layer, Agent Manager, and WebView support for the listed agents: Roo Code, Cline, and Kilo Code. It is delivered as a JetBrains Marketplace plugin, a ZIP release, or a source build. It fits teams that want to keep a JetBrains-centered development environment while using these specified VS Code agent integrations.
The JetBrains Plugin provides IDE integration, UI Integration, and an Editor Bridge, then communicates by RPC with the Node.js Extension Host. The host includes main.ts, extensionManager.ts, rpcManager.ts, and webViewManager.ts, alongside the VSCode API Layer, Agent Manager, and WebView support. This bridge is intended to run VS Code coding agents within a JetBrains IDE; the README names Roo Code, Cline, and Kilo Code. Cline is specifically described as being able to create or edit files, execute commands, and use the browser with permission at every step; that description is evidence for Cline, not a blanket guarantee for every supported agent.
- A Java engineer using IntelliJ IDEA who wants to use Roo Code without moving their project workflow to VS Code.
- A JavaScript or TypeScript team working in WebStorm that needs to bring Cline into its existing IDE.
- A Python developer in PyCharm who wants to run Kilo Code from the same IDE.
- A team standardizing across PhpStorm, RubyMine, CLion, GoLand, DataGrip, Rider, or Android Studio while adopting VS Code-oriented coding agents.
- A contributor debugging the bridge locally by running npm run dev in extension_host and ./gradlew runIde in jetbrains_plugin.
What are this agent's strengths and limitations?
- Uses a purpose-built Kotlin JetBrains Plugin plus Node.js Extension Host architecture to bridge JetBrains IDEs and the VS Code extension ecosystem.
- Explicitly uses RPC over Unix Domain Sockets or Named Pipes for local inter-process communication.
- Documents support across a broad set of JetBrains products, including IntelliJ IDEA, WebStorm, PyCharm, CLion, GoLand, Rider, and Android Studio.
- Names Roo Code, Cline, and Kilo Code as supported agents and includes WebView support in the documented architecture.
- Its operating boundary depends on the JetBrains IntelliJ Platform and Node.js, rather than being a standalone CLI or hosted agent service.
- It requires JetBrains IDE 2023.1+; source builds additionally require Node.js 18+, JDK 17+, Git, npm/pnpm, Gradle, and shell scripts.
- The material does not document post-install configuration, how the agent extensions are obtained, a first invocation, or credential setup.
- A known-issues document is referenced but its contents are not supplied, so common failure modes, limitations, and recovery guidance cannot be assessed.
How do you install or deploy this agent?
Recommended: in a compatible JetBrains IDE, open Settings/Preferences → Plugins, search Marketplace for “RunVSAgent,” select Install, and restart when prompted. Alternatively, download the ZIP from GitHub Releases, choose Settings/Preferences → Plugins → the gear menu → Install Plugin from Disk..., select the ZIP, and restart. Source builds require Node.js 18.0+, a JetBrains IDE 2023.1+, Git, and JDK 17+: run git clone https://github.com/your-org/RunVSAgent.git, enter RunVSAgent, then run ./scripts/setup.sh and ./scripts/build.sh. The built plugin is placed in jetbrains_plugin/build/distributions/. The supplied material does not document how to install, configure, or first launch Roo Code, Cline, or Kilo Code after the plugin is installed, nor does it state required credentials.
How do you use this agent?
After installation and IDE restart, the README states that Roo Code, Cline, and Kilo Code can run in JetBrains IDEs, but it does not provide a menu path, configuration keys, extension acquisition procedure, or a first copyable agent invocation. A first agent run therefore cannot be verified from the supplied material. For development, run npm install followed by npm run dev in extension_host, then run ./gradlew runIde in jetbrains_plugin.
How does this agent compare with similar options?
Compared with running these coding agents directly in VS Code, RunVSAgent is positioned as a bridge that brings specified VS Code agents and extensions into JetBrains IDEs through a JetBrains Plugin, Node.js Extension Host, and VSCode API Layer. No feature or performance benchmark is provided.