Daily · Article 03 · 4 min read
- Open source
- OpenAI
OpenAI plans to acquire code-review toolmaker Pierre: existing tools and future integration
Acquisition announcement dated November 4 · tools and license checked November 5 JST
Summary
OpenAI announced its planned Pierre acquisition on November 4. Trees and Diffs already used in Codex, separate code storage and future integration have different roles and delivery states.
When an AI changes many files, people still need to read the changes and decide which ones to accept. On November 4, OpenAI announced plans to acquire Pierre Computer Company, which builds code-storage and review tools. The announcement connects tools already used in Codex with a proposed future integration.
Key facts
OpenAI says the Codex app already uses Pierre's Trees and Diffs libraries for file navigation and change review. A library is a code tool that developers incorporate into an application. The new announcement adds a direction for joint development to that existing use. OpenAI announcement
Closing remains subject to customary conditions, including regulatory approvals; the companies remain independent until then. OpenAI says the open-source projects will remain open and customers can continue using Code Storage after closing while its features are brought into Codex. The announcement supplies no price or specific integration launch date.
1. Finding files, reading changed lines and keeping history
A web service's code is divided among files handling screens, calculations and settings. Git keeps version history showing how files changed. That supplies a basis for review, but people also need an interface for finding the relevant files and changes.
Trees displays the folder-and-file hierarchy, while Diffs presents before-and-after changes. Diffs' Edit feature lets a reviewer correct a line where they spot a problem. Code Storage provides Git-based repositories and history for applications. The interface components and the storage service have different jobs. Trees · Diffs · Code Storage
| Tool | Evidence a person can read | Work still required |
|---|---|---|
| Trees | Locate the relevant folder and file | Decide whether the change matches the request |
| Diffs | Read old and new content together | Test conditions and calculations |
| Code Storage | Retrieve stored files and change history | Review approval and live-service deployment |
- Tool
Trees
- Evidence a person can read
- Locate the relevant folder and file
- Work still required
- Decide whether the change matches the request
- Tool
Diffs
- Evidence a person can read
- Read old and new content together
- Work still required
- Test conditions and calculations
- Tool
Code Storage
- Evidence a person can read
- Retrieve stored files and change history
- Work still required
- Review approval and live-service deployment
The cat asks Q&A
The researcherWhat should a non-developer receive when commissioning a change?
Pocket NotebookAsk for the changed behavior, old and new conditions, and test results alongside the final screen. A file-comparison view can help a developer explain what changed. A tidy review screen alone does not establish correct ordering or payment rules.
2. A fictional shipping-fee change
Suppose an imaginary shop requests free shipping only for orders of at least 50,000 won. A comparison showing a fee changed from 5,000 won to zero leaves a question: did the change preserve that threshold, or make every order free? These amounts and this task are explanatory, not an observed Pierre or Codex run.
The person specifies the requirement, then checks that the comparison retains its condition. Testing orders of 49,999 won and 50,000 won illustrates what happens at the boundary. Connecting the saved code version to the tested version lets the next person compare the same result.
%% People, AI and verification in a fictional shop change · editorial explanation
flowchart TD
A["Person: specify shipping rule<br/>Free only from 50,000 won"] --> B["AI: propose code changes<br/>Show files and modifications"]
B --> C["Person: review before and after<br/>Judge whether the condition remains"]
C --> D["Tests and history: compare boundary orders<br/>Record reviewed version and results"]
D --> E["Operator: verify after deployment<br/>Read the result in actual ordering"]The cat asks Q&A
- The researcher
How can I trace an edit in the review screen to the live service?
Pocket NotebookFollow the application's saving, review and deployment records. Diffs supplies an editing interface, while the application determines how a change reaches the service. For a commissioned task, ask for a connection between the version tested and the version published.
3. Existing components and post-acquisition plans
The earlier Pando report concerned OpenAI's internal infrastructure for many engineers' and agents' Git operations. The Pierre announcement concerns connecting navigation, review and storage more closely with Codex. It does not launch Pando for outside customers or establish that every Code Storage feature is already in Codex.
Pierre's public repository specifies Apache 2.0. That governs public code use, rather than setting a hosted service's prices. Code Storage describes usage-based charges for storage and reads/writes, so a team considering adoption also needs to examine storage location, permissions, migration paths and contract terms. Repository license
| State described | Established scope | Evidence for the next decision |
|---|---|---|
| Current use | OpenAI says Trees and Diffs are used in Codex | Review features and results required for your task |
| Proposed acquisition | Closing conditions remain; companies operate independently | A subsequent closing announcement |
| Future integration | Plan to bring Code Storage functionality into Codex | Released scope, terms and availability date |
- State described
Current use
- Established scope
- OpenAI says Trees and Diffs are used in Codex
- Evidence for the next decision
- Review features and results required for your task
- State described
Proposed acquisition
- Established scope
- Closing conditions remain; companies operate independently
- Evidence for the next decision
- A subsequent closing announcement
- State described
Future integration
- Established scope
- Plan to bring Code Storage functionality into Codex
- Evidence for the next decision
- Released scope, terms and availability date
The cat asks Q&A
- The researcher
Which later notices should an existing Code Storage customer watch?
Pocket NotebookThe announcement says customers can keep using it after closing. Later contract notices and export or synchronization terms will help a customer assess their choices.
To close
Changes that remain reviewable
More generated code makes it increasingly important to connect a person's requirements with the actual modifications. The proposed acquisition aims to bring more review and storage tooling into Codex; later releases will establish which new capabilities users can actually access.
Sources
- OpenAI announcementopenai.com
- Treestrees.software
- Diffsdiffs.com
- Code Storagecode.storage
- Repository licensegithub.com