It’s mainly for performance. Otherwise, running the same mutated test multiple times is not going to be practical

Cool. The way the Plugin API is set up, remote execution works with no extra effort required by the plugin author. Build logic is broken up into several composable steps via “rules”. Things like subprocesses are hermetic. The engine will send relevant work to the remote workers for you. The only challenge is for the end-user to hook up remote execution, i.e. get their config and env working. Tom is working on some docs for that.