The runtime · YOLO mode
Hand it the wheel — safely.
Full autonomy over the whole loop, bounded by a sandbox that makes the worst case boring.
Autonomy and safety are usually sold as a trade-off: the more freedom you give an agent, the more damage it can do. Perslis refuses that trade. YOLO mode lets the runtime drive the entire loop — plan, build, verify, ship — without stopping to ask, while every action it takes is confined by a deny-by-default sandbox. Freedom is at the level of decisions; the blast radius is fixed at the level of permissions. The result is speed you can actually turn on, because the worst it can do is nothing dangerous.
Why "just let it run" usually terrifies people
Most autonomous agents are frightening for a good reason: they run with the operator's full privileges. A confident wrong step can delete files, hit production, or leak a secret — and nobody was watching. So teams either babysit every action (and lose the point of autonomy) or turn it off. Neither is a real answer.
Perslis's answer is to separate the two things that got tangled together: how much it decides on its own and how much it's allowed to touch. Turn the first all the way up; keep the second locked down.
Figure 1 — Autonomy on top, confinement underneath. The loop runs free; the sandbox fixes the blast radius.
Full autonomy — one command, whole job
Tell Perslis to go and it drives end to end: it plans the work, does it, verifies the result, and ships — no approval prompt on every step, no babysitting. For long or repetitive jobs this is the difference between a tool you supervise and a runtime that just gets it done.
Fail-closed by design
Autonomy is forced into a sandbox — it isn't an opt-out. Host control is deny-by-default: Perslis can only touch the paths and run the commands it was explicitly granted, and reversibility-classified actions are checked before they execute. If a permission wasn't given, the action simply can't happen. "Fail-closed" means the default on any uncertainty is no, not yes.
Proven before it ships
Speed is worthless if it skips the check. Even on autopilot, work has to pass the same verification gate as everything else before Perslis calls it done — the tests run, the invariants hold, the evidence is sealed. YOLO mode removes the prompts, not the proof. You get autonomous throughput without lowering the bar for what counts as finished.
When to hand over the wheel
YOLO isn't the only mode — it's the far end of a dial. Early on you watch closely; as trust builds and the sandbox is scoped right, you let more run unattended. Because the safety floor doesn't move as autonomy rises, you can turn up speed exactly as fast as your confidence grows — and no faster than the permissions allow.