Pretty cool, I’m excited to try this.

The WASM boundary as a security primitive is underappreciated most people reach for containers without asking whether the threat model actually requires a persistent process. On the 10 strategies question: Supervisor and Mixture of Experts will cover 80% of real workloads in my experience, with Debate and Reflection worth keeping as the next tier since Debate surfaces assumptions single-agent pipelines miss and Reflection catches compounding errors cheaply. The part I would stress test is the export-to-Python parity keeping browser prototype behavior identical to the deployed artifact is a hard problem, and curious how you are handling edge cases where Pyodide’s stdlib coverage diverges from CPython.

Multi-agent + MCP in a browser tab is a clean demo surface. The question I'd ask: does the studio represent agent topology as data (so you can serialize / version/diff it) or is it implicit in the UI graph? We found the former matters a lot the moment you want to test the same workflow against two different models, or roll back a change someone made in prod.

Great curious to try it out. Have you posted on Linkedkin as well ?