OpenAI announced plans on November 4, 2026, to acquire Pierre Computer Company, whose tools help software teams browse, review and store code. For Codex users and Code Storage customers, this is a proposed acquisition—not a new integrated service.
The deal still needs regulatory approvals and other closing conditions. OpenAI says the companies will operate independently until it closes.
What Codex already uses
OpenAI says the Codex app already uses Pierre’s Trees and Diffs libraries.
Trees displays a project’s files and folders; Diffs shows changes between versions of a file. These are open-source building blocks for software interfaces. A clearer view of a change helps someone inspect it; it does not establish that the code is correct.
Code Storage does a different job: it hosts repositories—the files and recorded history of a software project. Its documentation describes creating repositories, recording changes, combining branches and saving an AI agent’s intermediate work using Git, the version-control system.
What is promised after closing
OpenAI says Pierre’s open-source projects will retain that status, with continued contributions. It also promises continued Code Storage access after closing while it works to integrate the service’s capabilities into Codex.
The announcement gives no purchase price, closing date, integration timetable or new Codex pricing. Future Code Storage pricing and account arrangements are also unspecified.
What customers can decide now
Open-source libraries and hosted storage are separate choices. Code Storage’s pricing page, checked on November 4, lists monthly minimums of US$20 for Starter and US$200 for Scale. Customers pay the minimum or their metered usage, whichever is higher—not both added together. These are storage-service prices, not Codex subscription rates.
Using that service also need not mean leaving GitHub. The documented GitHub App sync keeps GitHub as the authoritative repository and forwards ordinary pushes there, with the necessary permissions. The public-import mode is different: it copies a public repository once, without continuous synchronization.
For software teams, the practical distinction is between an interface component, paid hosting and a coding-agent account. Evaluate each against its current features and terms; the proposed acquisition alone does not establish a reason to move repositories or buy additional access.
For teams reviewing a plan before code is written, RohitAI’s guide to getting a second AI opinion in VS Code covers a separate workflow—not a feature of the Pierre deal.