u/Aldgar

Hi Everyone,

I am the founder and creator of OXP, that is designed to use WASM and WASI to allow extensions to be build once, in any language from TypeScript, Java, or Rust and run it across all IDEs, VS Code, JetBrains, Cursor and Neovim.

The idea came from frustration of trying to build a private extension that can serve personal needs and to be more efficient in development and then we end up building OXP.

It was to build one extension to run across all IDEs and eliminate the need to build 5 to 6 versions for the same extension to run it in all,

it complies your extension logic in one WASM model and use bidirectional IPC bridge to translate native IDE API calls on the fly.

The MCP, it was completely a fix based on OXP architecture, as OXP allows one command and your MCP is running with your AI directly without configuration as OXP handles the hustle and configurations, as one command can run across all IDEs.

I wanted to share my architecture and we welcome any feedback from any kinds, so that we continue to improve it.

Thank you all for your support.

https://reddit.com/link/1tj89vy/video/898i6zwnte2h1/player

Hey Folks,

This project started because I simply wanted to build a new IDE to fix my own workflow bottlenecks. But I immediately hit a brick wall trying to build the tooling for it. I spent months, days, and nights trying to hack and fix VS Code extension webviews just to get a decent UI to render.

I realized I was fighting a 33 year old architectural problem: extension vendor lock in. If you want your dev tool to reach people today, you have to write Electron/TypeScript for VS Code/Cursor, and Kotlin/JVM for JetBrains.

So I stopped building the IDE, and I built the fix instead.

Meet OXP (Open eXtensions Protocol).
OXP is an open source universal standard that lets you write your extension once in React/WASM and run it natively across every major editor.

How I fixed the Webview problem:
This isn't a slow iframe hack. OXP uses a secure WebAssembly sandbox and a zero-latency IPC bridge. Your React code triggers an action, and OXP translates it to native IDE commands.

In VS Code, it binds directly to the native extension API.

In JetBrains, it uses JCEF to render as a native floating OS window.
You get blazing fast native speed from a single codebase.

**The Accidental MCP Fix:

While building this universal host layer, I realized OXP perfectly solves the current Model Context Protocol (MCP) configuration hell.

Instead of manually editing configurations for Cursor, Copilot, and JetBrains individually, OXP acts as a system level MCP router. If you run oxp install-mcp extension, the OXP daemon instantly wires that database context into the AI configurations of every detected IDE on your machine.

I'm opening up the infrastructure today. The CLI is live, and you can test it on your machine right now.

I'll be in the comments all day to talk about the WASM bridge, IPC latency, fighting with JCEF, and why extension silos need to die.

I was building an IDE to fix real mess and issues I was myself facing and one of them was to build extension for vscode, vscode forks, jetbrain, novim and zed, so I thought why not building an extension protocol that fix this issue!

Its finally hear, the battle-neck is kinda finished!

Not only extensions but also MCPs one command Boom works in your AI.

Its finally hear, the battle-neck is kinda finished!

Not only extensions but also MCPs one command Boom works in your AI.

Hey Folks,

This project started because I simply wanted to build a new IDE to fix my own workflow bottlenecks. But I immediately hit a brick wall trying to build the tooling for it. I spent months, days, and nights trying to hack and fix VS Code extension webviews just to get a decent UI to render.

I realized I was fighting a 33 year old architectural problem: extension vendor lock in. If you want your dev tool to reach people today, you have to write Electron/TypeScript for VS Code/Cursor, and Kotlin/JVM for JetBrains.

So I stopped building the IDE, and I built the fix instead.

Meet OXP (Open eXtensions Protocol).
OXP is an open source universal standard that lets you write your extension once in React/WASM and run it natively across every major editor.

How I fixed the Webview problem:
This isn't a slow iframe hack. OXP uses a secure WebAssembly sandbox and a zero-latency IPC bridge. Your React code triggers an action, and OXP translates it to native IDE commands.

In VS Code, it binds directly to the native extension API.

In JetBrains, it uses JCEF to render as a native floating OS window.
You get blazing fast native speed from a single codebase.

**The Accidental MCP Fix:

While building this universal host layer, I realized OXP perfectly solves the current Model Context Protocol (MCP) configuration hell.

Instead of manually editing configurations for Cursor, Copilot, and JetBrains individually, OXP acts as a system level MCP router. If you run oxp install-mcp extension, the OXP daemon instantly wires that database context into the AI configurations of every detected IDE on your machine.

I'm opening up the infrastructure today. The CLI is live, and you can test it on your machine right now.

I'll be in the comments all day to talk about the WASM bridge, IPC latency, fighting with JCEF, and why extension silos need to die.

Hey Folks,

This project started because I simply wanted to build a new IDE to fix my own workflow bottlenecks. But I immediately hit a brick wall trying to build the tooling for it. I spent months, days, and nights trying to hack and fix VS Code extension webviews just to get a decent UI to render.

I realized I was fighting a 33 year old architectural problem: extension vendor lock in. If you want your dev tool to reach people today, you have to write Electron/TypeScript for VS Code/Cursor, and Kotlin/JVM for JetBrains.

So I stopped building the IDE, and I built the fix instead.

Meet OXP (Open eXtensions Protocol).
OXP is an open source universal standard that lets you write your extension once in React/WASM and run it natively across every major editor.

How I fixed the Webview problem:
This isn't a slow iframe hack. OXP uses a secure WebAssembly sandbox and a zero-latency IPC bridge. Your React code triggers an action, and OXP translates it to native IDE commands.

In VS Code, it binds directly to the native extension API.

In JetBrains, it uses JCEF to render as a native floating OS window.
You get blazing fast native speed from a single codebase.

**The Accidental MCP Fix:

While building this universal host layer, I realized OXP perfectly solves the current Model Context Protocol (MCP) configuration hell.

Instead of manually editing configurations for Cursor, Copilot, and JetBrains individually, OXP acts as a system level MCP router. If you run oxp install-mcp extension, the OXP daemon instantly wires that database context into the AI configurations of every detected IDE on your machine.

I'm opening up the infrastructure today. The CLI is live, and you can test it on your machine right now.

I'll be in the comments all day to talk about the WASM bridge, IPC latency, fighting with JCEF, and why extension silos need to die.