On November 4, 2026, OpenAI announced plans to acquire Pierre Computer Company. The announcement separates two things developers might otherwise lump together: Pierre’s libraries already used in Codex and the planned integration of features from Pierre’s Code Storage service. OpenAI said the companies would remain separate until the deal closes.

A developer reviewing code changes at a workstation.
A developer reviewing code changes at a workstation.

File review and repository storage are separate

OpenAI says Codex already uses Trees to help people browse project files and Diffs to show code changes. Those libraries help users inspect a project. Code Storage is a separate service that lets applications store code and track its Git history. Seeing a diff in Codex does not by itself identify where the repository is hosted.

What teams should check before changing a workflow

OpenAI says Pierre’s open-source projects will stay open source and that Code Storage customers can continue to use the service after closing while OpenAI works to bring its features into Codex. The announcement does not give a date for a general migration or tell customers to move their repositories now.

For example, a fictional team reviews a change in Codex and merges it through its existing Git host. It should record where the remote repository lives, who controls merge permissions and where the review record is kept. If a future integration changes any of those answers, evaluate that change on a test repository before changing a production workflow. No migration or product integration was tested for this article.

If you evaluate a different Git host or mirror, use the repository pilot checklist to check large-file downloads, exact revisions and CI results separately.

OpenAI’s November 4 Pierre acquisition announcement

What does the announcement confirm?