I don't often run into errors at jack-in but it always irritated me that I had to go digging in windows I don't normally have open in order to figure out why, so that's a very welcome improvement! Thank you!

A thing to note here is that what we do is to match the stderr from the jack-in process for /error|exception/ and if that happens before the repl server starts, we pop up that dialog. So some project where output like that is happening as part of starting the repl, without it causing a the repl start to fail, it may be a bit spammy. OTOH, I think is worth trying to clean the start up from such messages anyway. Let’s see if we will need to tune.

Ah, interesting approach.

Thanks. I took the hint, @U04V70XH6 😃 https://clojurians.slack.com/archives/CBE668G4R/p1720641947181189