Using postMessage, send data back and forth dynamically between embeded iframe and parent window. This way, the sandbox could send logs and error messages to parent for custom handling. The parent could also send data to be received by the sandbox and dynamically update the interpreter contents. Iframes are hard to customize and query parameters only allow customization on initialization, but postMessage could introduce a variety of dynamic customization options.
Embeds are traditionally tied to persisted projects. Inlined project data passed on the embed url would allow the embedding site to own the code and a sandbox would only be persisted in StackBlitz at the point that the embed is forked. This is powerful for documentation sites so they don't have to be updating their code snippets in multiple places and instead they can have a single source of truth for their code snippets. It also would allow auto-updating dependencies. So