The Wire · Showcase
CODEX TIGHTENS GOAL STATE CONTROL ACROSS FIVE CORE CHANGES
By RepoJournal · Filed · About OpenAI
Codex shipped explicit pause semantics and plugin architecture refactors that stop goals from silently pausing when users didn't ask for it.
The biggest fix kills the implicit pause problem [1], where guardian approvals, server shutdowns, and steering interrupts could pause active goals without explicit user action. That's now locked down: pause transitions require deliberate intent. Running parallel with that, goals now respect usage limits and blockers [2] instead of burning tokens on turns that can't progress, moving into resumable `blocked` and `usageLimited` states that halt continuation loops. On the orchestration side [3], turn skill and plugin injection got extracted from the bloated `run_turn` method into a cleaner `build_skills_and_plugins` handler, making the control flow readable without losing the ordering guarantees that matter. The session picker now actually accepts paste events [4], collapsing whitespace and routing bracketed pastes into search the way users expect, fixing the macOS terminal experience where pasting looked like a no-op. Finally, renamed thread hints got clarified [5] to include thread IDs in parentheses, killing the ambiguity when multiple threads share a name and users try to resume by the picker.
Action items
- → Review goal pause logic in your active codex instances to surface any implicit pauses your users haven't reported yet openai/codex [plan]
- → Test session picker paste behavior on macOS terminals to confirm the whitespace normalization works for your use case openai/codex [monitor]
- → Update any resume documentation or hints that reference thread names without IDs openai/codex [plan]
References
- [1] goals: keep pause transitions explicit ↗ openai/codex
- [2] goal: pause continuation loops on usage limits and blockers ↗ openai/codex
- [3] [codex] Extract turn skill and plugin injections (#23396) openai/codex
- [4] feat(tui): handle paste in session picker ↗ openai/codex
- [5] Clarify resume hints for renamed threads ↗ openai/codex
FAQ
- What changed in OpenAI on May 19, 2026?
- Codex shipped explicit pause semantics and plugin architecture refactors that stop goals from silently pausing when users didn't ask for it.
- What should OpenAI teams do about it?
- Review goal pause logic in your active codex instances to surface any implicit pauses your users haven't reported yet • Test session picker paste behavior on macOS terminals to confirm the whitespace normalization works for your use case • Update any resume documentation or hints that reference thread names without IDs
- Which OpenAI repositories shipped on May 19, 2026?
- openai/codex