What should OpenAI teams do about it?

Review skills invocation patterns in your executor if you're hosting plugins • Upgrade Node CI workflows to use ci environment scope for OPENAI_API_KEY • Update Python CI workflows to use ci environment scope for OPENAI_API_KEY

Which OpenAI repositories shipped on June 12, 2026?

openai/codex, openai/openai-node, openai/openai-python

CODEX DECOUPLES SKILLS FROM EXECUTOR, NODE AND PYTHON TIGHTEN CI SECURITY

By RepoJournal · Filed 06:03 UTC on June 12, 2026 · About OpenAI

Codex shipped a breaking refactor that makes hosted plugin skills invocable without an executor, while both Node and Python SDKs locked down their CI workflows to use scoped API key environments.

The codex team landed three interconnected changes that fundamentally reshape how skills integrate with the runtime. First, backend plugin skills are now invocable without an executor [1], which means app-server can properly surface hosted skills in the model's catalog and load their metadata through the `$skill` interface. Second, the skills catalog now renders locators by authority [2], telling the model whether a skill lives on disk or must be fetched through a remote source. Third, ThreadStore now owns persistence policy application [3], enabling store-specific projections over raw input. In parallel, ExecutorFileSystem is being migrated to PathUri [4] as the canonical internal path representation, with EnvironmentPathRef removed entirely [5]. On the SDK side, both openai-node and openai-python tightened their CI workflows to use scoped GitHub environments for API key access [6] [8], and the Node team bumped CI coverage to Node 20, 22, 24, and 26 [7], moving the default test line to Node 24 LTS. These aren't cosmetic updates: the codex changes fix a real gap where hosted skills were described as local files, and the SDK CI changes prevent API keys from being accessible to untrusted workflow contexts.

FAQ

What changed in OpenAI on June 12, 2026?: Codex shipped a breaking refactor that makes hosted plugin skills invocable without an executor, while both Node and Python SDKs locked down their CI workflows to use scoped API key environments.
What should OpenAI teams do about it?: Review skills invocation patterns in your executor if you're hosting plugins • Upgrade Node CI workflows to use ci environment scope for OPENAI_API_KEY • Update Python CI workflows to use ci environment scope for OPENAI_API_KEY
Which OpenAI repositories shipped on June 12, 2026?: openai/codex, openai/openai-node, openai/openai-python

CODEX DECOUPLES SKILLS FROM EXECUTOR, NODE AND PYTHON TIGHTEN CI SECURITY

The showcase is a teaser. Your wire is the product.

The showcase is a teaser.
Your wire is the product.