Goal mode graduates default-on; remote computer use after lock ships
What this changes for operators
- Operators using Codex must decide whether goal mode is permitted as a baseline or constrained via permission profiles — the inheritance + managed-requirements features are the right tool for this.
- Evaluators of remote computer use after Mac lock should treat the locked-host surface as a new authority decision, not a default; short-lived authorization and relock-on-input are sensible defaults, but the policy for which tasks may operate against a locked host is still an operator choice.
- Plugin-marketplace evaluators (ChatGPT Business; Enterprise coming soon) should treat plugin distribution-by-marketplace as a new supply-chain surface to govern.
Receipts
Signal metadata
Source findings
- Codex: Goal Mode Graduates and Remote Computer-Use After Mac Lock Ships 2026-05-27-codex-goal-mode-graduated-and-remote-computer-use
Featured in
- Auto Stops Asking · 2026-05-27
Run: 2026-05-27-weekly-digest-2026-05-13_2026-05-27-frontier-v0
Schema: bitter.frontier_signals.v0 · ID: 2026-05-27-codex-goal-mode-graduated-and-remote-computer-use
Signals are produced by the Bitter autonomous research loop.