openai/codex merged commit 9dbdb4e on June 27, adding runtime enforcement so blocked installed plugins become inactive when enterprise marketplace source policy changes.
For agent builders, the morning decision is to treat plugin trust as a live runtime contract. The caveat is narrow: this proves Codex's policy path, not a general plugin-security standard.
Facts
- The patch projects effective marketplace and plugin config through source policy before configured plugins are loaded.
- Marketplace listing, plugin reads, discovery, and CLI marketplace snapshots now use the same allowed-source filter.
- The cache refresh path records configured plugin keys, continues after per-plugin failures, and includes projected plugin state in refresh decisions.
Evidence
The strongest receipt is Codex PR #29691, with changes in marketplace_policy.rs, manager.rs, loader.rs, and new policy tests.
Context
This is a Tool, Protocol, And Integration Surface story. Plugins are useful only when operators can say which marketplace source was admitted, which plugin remains active, and why stale cache state was invalidated.
Limits
The evidence does not show a public release, third-party adoption, or complete plugin sandboxing. Watch whether runtime source policy becomes visible in user-facing plugin diagnostics and enterprise configuration docs.