OpenAI to acquire Pierre Computer: Codex wants your repo

OpenAI will acquire Pierre Computer, the small startup behind Code Storage and the open-source Trees and Diffs libraries, OpenAI announced November 4. Axios broke the deal first and framed it as a move against Microsoft's GitHub. Terms were not disclosed. If you have reviewed a change inside the Codex app, you have already run Pierre's code. Now OpenAI wants the layer underneath: the place where the repository lives.

What actually happened

OpenAI's post lists what it is buying. Trees navigates a project's files. Diffs shows what changed, and its Edit mode lets a reviewer fix a line without leaving the diff. Code Storage is the piece that matters: OpenAI describes it as "a service that lets apps store code and track its history using Git."

The commitments are specific. Pierre's open-source projects stay open source, and OpenAI says it will keep contributing to them. Code Storage customers can keep using the service after the deal closes "while we work to bring its features and functionality into Codex." Closing depends on regulatory approvals, and the two companies stay separate until then.

On November 2, OpenAI published Scaling Git at OpenAI, describing Pando, an in-house Git backend built because Codex-driven parallel work pushed its monorepo's reliability "at times below 90%." Pando cut median push latency by nearly 5x and now serves close to a petabyte of Git data a day, while staying compatible with the standard Git client. The Pierre post names Pando and says the goal is to "make Codex the place where developers and agents take on their most ambitious projects."

Why it matters for your business

Most small-business code lives on GitHub, and that is where Copilot, Claude Code and Codex push. Codex already runs your dev setup on OpenAI's VMs through cloud environments. Add code storage and one vendor holds the environment, the review surface and the repository. Convenient, until the pricing, the quota or the terms change, and all three have changed in the last month.

The good news is in the engineering. Pando and Code Storage both speak the Git protocol, so a plain git clone is your exit. Our rules:

• Keep a second remote. A nightly git push --mirror to a different host costs nothing and makes the acquisition question moot.
• Avoid features that do not export. Hosted review threads, agent-only history, annotations that live in the vendor's database. If it is not in the Git objects, assume you lose it on the way out.
• Watch the Code Storage arc. Standalone continuity until the features "move into Codex" is how every acquired dev tool goes. Plan for the Codex version, not the Pierre version.

Sources: OpenAI, "OpenAI to acquire Pierre Computer Company, Inc.", OpenAI, "Scaling Git at OpenAI", Axios.