All activity
A real Codex runtime in the browser — with explicit control over what it’s allowed to do.
XCodex runs the actual Codex core in WASM and executes locally with browser-native capabilities like DOM inspection, storage access, and network requests.
The runtime is designed to be embedded — consumers define what the agent is allowed to do via capability controls, origin policies, and approval flows for high-trust actions.
No backend. Execution happens entirely in your browser.
XCodex WASMCodex running in your browser. No backend.
Oleg Romanchukleft a comment
Hey everyone 👋 I built XCodex WASM around a simple idea: What if the Codex runtime actually ran inside the browser? Not behind an API. Not on a server. Right next to the page it works on. Once you do that, everything changes. The agent doesn’t call tools somewhere else — it operates directly on its environment: • the current page (DOM, UI, interactions) • local workspace and files • browser...
XCodex WASMCodex running in your browser. No backend.