Oxide

Oxide — A Binary-First Browser with AI-Native App Generation What it is: Oxide is a decentralised browser written from scratch in Rust that throws out HTML, CSS, and JavaScript entirely. Instead of fetching markup, it fetches .wasm files and runs them directly. Every web page is a sandboxed WebAssembly module with capability-based access to ~150 host functions covering canvas, GPU, audio, video, WebRTC, WebSockets, MIDI, media capture, storage, and more. Oxide Forge is the AI-native layer built on top: you type a sentence in plain English, Claude Opus 4.7 writes the Rust source, cargo compiles it to wasm32-unknown-unknown, running the freshly minted app — inside the same airtight sandbox as everything else. If the build fails, Forge feeds the compiler output back to Claude up to 3 times until it compiles. One sentence in. One real, sandboxed application out. The problem it solves: The web's foundation — HTML + JS + a permissive DOM — was designed for hyperlinked documents, not for a world where non-programmers generate software on demand from natural-language prompts. Two real problems collide today: The web stack is the wrong substrate for AI-generated code. JavaScript apps can phone home, exfiltrate tokens, abuse APIs, or run forever. Permission models are subtractive (claw back what was already granted) and fragile. The next billion "developers" aren't developers. Teachers, doctors, students, and hobbyists are about to author software through LLMs. Handing them a system where every prompt has effectively root-level capabilities — DOM, fetch, eval, third-party scripts — is dangerous. Oxide flips both: Additive, not subtractive security. A guest module starts with zero capabilities. No filesystem. No env vars. No raw sockets. No WASI. If we didn't register it in the wasmtime linker, it doesn't exist. Memory is capped at 256 MB; execution is fuel-metered (500M instructions per call). The worst an AI-generated app can do is fail to compile or run out of fuel. A first-class target for code-generating LLMs. Because every app is a single self-contained .wasm, Claude Opus 4.7 has a clean, well-typed surface to target. The Forge prompt kit ships a curated CAPABILITIES.md, PATTERNS.md, and 12 runnable RECIPES.md — an Agent Skill — so the model produces idiomatic, compilable Rust on the first try, and self-corrects when it doesn't. Why it matters for the hackathon Oxide Forge is a concrete demonstration that Claude Opus 4.7 can be a co-creator of an entire computing platform, not just a code-completion engine: Claude writes the guest apps (via Forge). A large portion of the host browser itself — capabilities, runtime, examples — was built with Opus 4.7 as a pair-programming partner. The system prompt, skill, and self-debug loop are designed around how Opus 4.7 actually reasons about constrained Rust APIs. The result is a glimpse of the post-HTML web: the future of software is sandboxed binary, written by AI, and safe by construction. Managed agent also has been created in claude platform to write apps for oxide leveraging agent skill system.