Headless Does Not Mean Unconfigured

The upgrade stopped at action one

A launchd job that worked on 1.6 reached 1.7 RC11 and failed on co browser status. Auto required a live approval, stdin was closed, and the operator's standing command permission was ignored.

The tempting compatibility fix was too broad

Blindly honoring the historical Bash(co *) pattern would include deployment, email, account, server, and payment actions. Compatibility could not become an unattended escalation path.

Configuration is authority

Headless Auto now honors operator-authored command rules for ordinary commands. The shipped broad compatibility entry restores only co status and co browser .... Publication, deployment, unknown, destructive, credential, and external-effect calls keep their stronger verdicts.

Evidence and tradeoff

The exact no-IO path and a command chain pass, while co deploy, co publish, and co email send remain denied. Narrow operator rules are still authority; effect-typed permissions would eventually be clearer than command-text classification.

See co ai and tool approval.