On November 4, 2026, OpenAI announced plans to acquire Pierre Computer Company, Inc. and bring Pierre’s Code Storage features into Codex after the deal closes. The acquisition is subject to customary closing conditions, including regulatory approvals, and OpenAI said the companies would remain separate and independent until closing. OpenAI’s announcement describes Code Storage as a service for storing code and tracking its history with Git.
The proposed addition concerns where source code is stored and how its Git history is tracked. Deploying a finished app is a separate step.
What Codex already uses, and what Code Storage would add
OpenAI says Codex already uses Pierre’s Trees library to navigate project files and Diffs to view code changes. Code Storage is a separate service: Git records changes to code over time, so developers can track a project’s history. OpenAI plans to bring Code Storage’s features and functionality into Codex after the acquisition closes.
That distinction matters if you’re asking whether Codex’s existing Pierre tools mean Code Storage is already part of the product. Trees and Diffs are the components OpenAI names as already in use; Code Storage is the planned integration.
Kevin Stratvert’s earlier tutorial shows a Codex workflow connecting GitHub and tracking changes with Git. It predates the Pierre announcement and covers the existing workflow, not Code Storage.
What OpenAI said about customers and open-source projects
OpenAI said existing Code Storage customers can continue using the service after the acquisition closes while it works to bring the features into Codex. The company also said Pierre’s open-source projects will remain open source and that OpenAI will continue contributing to them.
