WeSearch

OXP – Write one WASM extension, run natively in VS Code, JetBrains, and Neovim

OXP Protocol· ·2 min read · 0 reactions · 0 comments · 32 views
OXP – Write one WASM extension, run natively in VS Code, JetBrains, and Neovim
TL;DR · WeSearch summary

The OXP runtime v0.1 has been released, allowing developers to create a single extension that runs natively across multiple IDEs, including VS Code, JetBrains, and Neovim. This new approach promises true portability with a universal API surface, eliminating the need for compromises or extensive tweaks. The OXP framework utilizes modern tools and offers features like sandboxed micro-frontends and native rendering.

Key facts
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
OXP · OXP Protocol
Read full at OXP →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherOXP
Canonical URLhttps://oxp.sh/
Publication timeSat, 16 May 2026 07:05:36 +0000
Retrieval time2026-05-16T07:40:17.734Z
Last seen2026-05-16T07:40:17.734Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster375lN3zKyV8I
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Runtime v0.1 shipped · VS Code · JetBrains · NeovimBuild one extension. Run across every IDE.VS Code · JetBrains · Neovim · Cursor · Windsurf — write it once, ship it everywhere on the open OXP runtime.KSearchPopular:reactpythonthemesgitaijupyter2,514MCP Servers5Compatible IDEsOpenProtocolBuilt inEuropeVS CodeVS CodeCursorCursorWindsurfWindsurfJetBrainsJetBrainsNeovimNeovimVS CodeVS CodeCursorCursorWindsurfWindsurfJetBrainsJetBrainsNeovimNeovimShipping nextv0.1 is live. v0.2 is already in flight.Specified in WIT. Implemented on all three hosts. Rolling out as soon as conformance tests go green — no waiting on a 2027 milestone.Native UI surfacesui/render painted into real tool windows on JetBrains and floating windows on Neovim.

Excerpt limited to ~120 words for fair-use compliance. The full article is at OXP.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from OXP