Going from "build and running executables" to that needing to be done on the same system and under control of the LLM is a large leap.

Separation of duties and ephemerality are well-known security mechanisms that many harnesses jump right over in the pursuit of easier UX.

Mingling permissions + trusting vibe-coded security boundaries in the harness itself (developed by folks whose appetite for risk would make even an 00s front-end developer blush) is rolling a handful of dice all at once.

But fundamentally, this is a disagreement between two risk appetites who will never agree: {it works most of the time} vs {it's guaranteed to never fail}