@volter/browser-python

The Pyodide execution engine for Browser Substrate. BrowserPythonCommand receives the selected provider's distribution; registerPythonPrograms registers its qualified command faces from runtime.baselines. installHostPython uses the same baseline on a Node host. Provider files and snapshot are prepared/published through the demand pipeline, verified before use, and kept separate from execution bridges. No default CDN/version or command list selects a runtime. The worker keeps the browser workspace coherent.

Supported application paths include scripts, python -c, static HTTP servers, Flask/WSGI, ASGI HTTP streaming and WebSockets, lifecycle events, SQLite file coherence, and routed subprocesses. Virtual servers use the same port and sandbox bridge as Node and WALI; they do not open a host-machine listener.

Python package installation/downloads, arbitrary socket listeners, editable/VCS installs, and direct wheel URLs are outside the current scope and fail explicitly.

Cross-origin workers deliberately disable SAB-backed cross-process SQLite coherence and Python subprocess routing because browsers do not clone shared memory across distinct origin agent clusters. Core Python execution, selected runtime loading, workspace synchronization, WSGI/ASGI/static servers, and brokered networking remain available. A same-origin embedding may opt into the shared memory channels when its credential model permits that trust boundary.