the setup, if present, inevitably runs before any related visual non-seutp editor code, so we can start one step at the time and see if it improves current state already? the rest might be done later on

Hello! I am also trying to automatically run the editor. I have tried a few ways, but haven't been able to get your snippet to work for me. Where exactly should the document.getElementById snippet you sent be placed? I tried placing it in a script tag of type py, as well as a normal script tag. Maybe you have a full example handy (a complete html snippet would be awesome)?

that-script is the id attribute of the editor ... <script type="mpy-editor" id="that-script"> as example

Thanks for your reply! I did have the id set and was referencing it. However, I am hitting a concurrency problem I believe - my snippet to click the button is running before the editor loads. How can I be sure to run that script after the editor has loaded?

you shouldn't need a script to override the Run button, there's a handleEvent API to do that you can attach to the script itself, but it's true that due MutationObserver asynchronous behavior, it's possible you indeed could have a race there.

(function behavior() {
  const script = document.getElementById('that-script');
  if (!script.target) return setTimeout(behavior);
  // the rest of your code
}());

This snippet might help you as it works only once the target field has been provided by PyScript.