OpenAI to acquire Pierre to bring Code Storage into Codex

The maker of the Trees and Diffs libraries already used in Codex joins OpenAI, and its open source projects stay open.

On November 4, 2026, OpenAI announced an agreement to acquire Pierre Computer Company, the startup behind Code Storage and the Trees and Diffs libraries that already power file browsing and change review in Codex. OpenAI plans to bring Code Storage into Codex. Financial terms were not disclosed and the deal still needs regulatory approval.

Key facts

OpenAI announced on November 4, 2026 that it will acquire Pierre Computer Company, Inc., a developer tools startup.
Pierre makes Code Storage, a service that lets applications store code and track its history with Git, plus open source libraries called Trees, Diffs and Highlights.
Trees and Diffs are already built into the Codex app, where they handle file navigation and the review of code changes.
Financial terms and a closing date were not disclosed. The deal is subject to customary closing conditions, including regulatory approvals, and the two companies stay independent until it closes.
Pierre’s open source projects will remain open source, and existing Code Storage customers can keep using the service.

What happened

OpenAI used its news page to announce the agreement with Pierre Computer Company, a small company focused on the tools developers use to look at, review and store code. According to StartupHub.ai, which reported on the announcement the same day, OpenAI said it wants to “set the standard for modern source control” and to connect the code a company ships with the decisions its people make.

Pierre’s products fit together. Trees gives a fast view of the files and folders in a project. Diffs shows what changed between two versions of the code, and includes an Edit mode for fixing a single line during a review. Highlights adds syntax coloring that updates while code is typed or streamed by an AI agent. Code Storage is the back end: it stores code and records its history using Git, the version control system most software teams already rely on.

Techgenyz notes that the deal is meant to push Codex beyond writing code and toward a broader development platform. OpenAI plans to bring Code Storage’s features into Codex, while current customers keep access after the acquisition. Both sources also mention Pando, a source control system OpenAI introduced earlier for engineers and agents working in parallel. Axios framed the deal as a move against Microsoft’s GitHub, but StartupHub.ai points out that OpenAI’s own post talks about adapting Git workflows for agents, not replacing GitHub.

Why it matters

Coding agents change how code gets written. Instead of one person making a few changes a day, several agents can open branches, write code and propose edits at the same time. That puts pressure on the tools that store code and show what changed, which were designed for human pace.

By buying the team behind the viewers Codex already uses, OpenAI is betting that reviewing and storing agent written code will become as important as generating it. For developers who use Codex, the practical promise is a tighter loop: browse files, read a diff, fix a line and keep history in one place.

For everyone else, the open questions matter as much as the deal. StartupHub.ai lists several: how agents will be identified as authors, what review and audit rules will apply, and how Code Storage will be priced once it moves into Codex. None of these has been answered yet.

How to try it

You do not need Codex to benefit from cleaner repositories. A clear README is the first thing any reviewer, human or agent, reads in a project. Our free Documentation for your project prompt turns what you already know about a project into a structured README, and marks gaps with visible TODOs instead of inventing details.

Open the prompt and fill in three fields: the project name and idea, what you know about it (requirements, how to install and run it, where settings live), and who will read it (non technical users, developers or both). For example: name “ShiftBoard, a small web app that turns a staff rota spreadsheet into a weekly calendar”, what you know “Node 20, install with npm install, start with npm run dev, settings in .env (sheet URL, time zone)”, readers “Both”.

Paste the result into ChatGPT, Claude or Gemini. Check that every command matches what you wrote, that nothing has been added that you did not mention, and that the TODO list at the end asks real questions you can answer. Then commit the README to your repository so the next person, or the next agent, starts from the same facts.

Try it

Documentation for your project

Frequently asked questions

What is Pierre Computer Company?

It is a developer tools startup that makes Code Storage, a Git based service for storing code and tracking history, and the open source libraries Trees, Diffs and Highlights. OpenAI's Codex app already uses Trees and Diffs for file browsing and reviewing changes.

How much is OpenAI paying for Pierre?

The price was not disclosed. OpenAI said the deal is subject to customary closing conditions, including regulatory approvals, and that Pierre and OpenAI will keep operating independently until the acquisition closes.

Will Pierre's open source tools stay free?

OpenAI says Pierre's open source projects will remain open source and that it will keep contributing to them. Existing Code Storage customers can keep using the service while its features are brought into Codex.

Sources