Skip to main content
Load an unpacked extension into a running browser — ad blockers, automation helpers, in-house tooling — without rebuilding the runtime image. The extension directory must live in the runtime’s workspace (put it there with runtime.files or runtime.exec). CLI and cURL examples use $RT and browser b1 (Sessions).

Load and unload

extension_load takes a workspace path containing a manifest.json and returns {extension_id} — keep it for extension_unload. Extensions survive navigations and new tabs in the same browser.
Extension loading works on the pipe transport that runs every Gravix browser — a capability that is unavailable over the usual WebSocket debugging channel. It requires a headed or headless=new browser, which is what browser.open always starts.