OpenAI says it will acquire Pierre Computer Company, the developer-tools startup behind Code Storage and several open-source Git libraries, and plans to bring more of its technology into Codex. Codex already uses Pierre’s Trees and Diffs libraries for navigating files and reviewing changes, according to OpenAI. The deal is not complete: it remains subject to customary closing conditions, including regulatory approvals, and the companies will operate separately until it closes.

What does Pierre Computer make?

Pierre Computer describes itself as a software company building infrastructure for machine-driven work. Its products include Code Storage, a service for storing code and tracking its history with Git, and open-source tools for working with code.

OpenAI says Codex already uses two of Pierre’s libraries. Trees helps people navigate project files. Diffs displays code changes, and its Edit mode lets a reviewer correct a line inside the change view. Pierre’s Highlights tool adds syntax coloring as a person types or an AI agent produces code. These are supporting components in a coding workflow, rather than a new AI model or a standalone coding assistant.

What could change in Codex?

OpenAI says it wants to build on Pierre’s Git workflows and bring Code Storage’s features into Codex after the acquisition closes. It has not announced a release date or a complete list of future capabilities. The company also says customers can continue using Code Storage after closing while it works on integration.

That means the immediate news is a proposed acquisition and a longer-term product direction—not a new Codex feature users can turn on today. OpenAI says Pierre’s open-source projects will remain open source and that it will continue contributing to them.

In an engineering post published on November 2, OpenAI described Pando, its in-house backend for Git repositories. The company said Codex has increased the amount of parallel software work its engineers do, creating more simultaneous branches, pushes and builds. Pando is an internal system described by OpenAI; the Pierre announcement does not say Code Storage will replace Git, GitHub or Pando.

Why the acquisition matters for software teams

AI coding tools are increasingly being built around a wider development process: not just generating code, but also navigating a repository, comparing edits and reviewing work. Pierre’s tools give Codex components for some of those tasks, while Code Storage may give OpenAI another way to connect code and its history inside the product.

For developers and businesses, the practical question is what OpenAI eventually ships and how it fits with existing Git hosting and review workflows. The company’s announcement signals its intent, but it does not yet establish whether teams will need to change their current tools or what any future integration will cost. OpenAI did not disclose financial terms or a completion date in its announcement.

The Wall Street Journal’s independent report likewise describes the deal as a planned purchase intended to improve Codex. The Decoder’s coverage details the libraries and notes that regulatory approval is still required.

Frequently asked questions

Has OpenAI completed its acquisition of Pierre Computer?

No. OpenAI announced that it will acquire Pierre, but the transaction is subject to customary closing conditions, including regulatory approvals. Until it closes, OpenAI and Pierre remain separate companies.

Are Pierre’s tools already part of Codex?

OpenAI says Codex already uses Pierre’s Trees and Diffs libraries. The company plans to bring Code Storage features into Codex after the acquisition closes, but has not provided a rollout date or full feature list.

Will Pierre’s open-source projects remain available?

OpenAI says Pierre’s open-source projects will remain open source and that it will continue contributing to them. The company also says customers can keep using Code Storage after closing while integration work proceeds.

Is Codex replacing GitHub or Git?

OpenAI has not announced a plan to replace Git or GitHub. The stated goal is to expand Codex’s tools for building, understanding and reviewing code, while working with Git workflows developers already use.