On November 4, 2026, Beijing time, OpenAI announced its intention to acquire Pierre Computer Company Inc. to expand the tools for code construction, understanding, and review within Codex. The transaction has not yet closed and is subject to customary closing conditions and necessary regulatory approvals. Until the closing is completed, OpenAI and Pierre will continue to operate as separate entities. The announcement confines the proposed integration to the scope of Codex and Git workflows, without declaring the transaction completed or providing regional product launch schedules. OpenAI has not specified which regulatory body will conduct the preliminary review.
Existing Integration Confirmed for Trees and Diffs
Pierre is the developer of Code Storage and other developer tools such as Trees, Diffs, and Highlights. OpenAI describes Code Storage as a service that allows applications to store code and track its history using Git. Trees are used to browse project files, while Diffs are used to view code changes, with its Edit mode allowing reviewers to modify code directly within the difference interface. Highlights is a syntax highlighting tool that updates as developers input or code agents generate content. The announcement does not group these different products into a single service and does not disclose user numbers or revenue for each product.
OpenAI confirmed that the Codex application is currently using Pierre's Trees and Diffs libraries: when users browse files or review changes in Codex, they interact with these technologies. The official announcement does not claim that Highlights has been deployed to Codex, nor does it state that Code Storage has been fully integrated. At this stage, the existing usage relationship of two review and navigation libraries can be confirmed, rather than the entire Pierre product line entering Codex; the announcement also does not provide usage scale or performance data for these two libraries within Codex.
Code Storage Plan Awaits Transaction Closing
According to the plan announced by OpenAI, after the transaction is closed, the company will work with the Pierre team to integrate Code Storage's features into Codex. The announcement did not disclose the acquisition price, payment method, expected closing date, or the specific version or migration timeline for Code Storage features entering Codex. The official statement also did not clarify whether the transaction would be paid in cash, equity, or another payment structure. Therefore, this remains an acquisition and product integration plan subject to closing conditions and should not be written as a completed technical merger; the scope and pace of any launch must await further official information.
OpenAI also stated that Pierre's open-source projects will continue to be open-source after the transaction is completed, and the company will continue to contribute code to these projects. For existing Code Storage customers, the announcement stated that they can continue to use the service after the acquisition is closed while OpenAI advances the integration of its features into Codex. The announcement did not specify the future governance of the open-source projects, whether the licenses would be adjusted, or disclose customer contracts, support periods, or migration options; these gaps cannot be rewritten to imply that the service will remain permanently unchanged or that there will be no interruptions during the integration period.
Company Explains Parallel Development Background but Does Not Provide Effectiveness Data
The rationale provided by OpenAI for the transaction is related to parallel development facilitated by code agents. The company states that as more engineering work is carried out simultaneously, systems around Git need to adapt to new working methods and aim to expand Codex's role from branch creation to code deployment in the processes involving developers and agents. These statements reflect OpenAI's purpose and product direction for the acquisition and are not independent evaluation conclusions; the announcement does not provide data on efficiency improvements, changes in reliability, or customer adoption following the acquisition.
The announcement also mentions Pando, disclosed by OpenAI on November 2. Pando is an internal source control backend built by OpenAI for engineers and code agents, which the company uses to illustrate its handling of Git scalability issues arising from parallel code work. The official announcement does not indicate any plans for merging, replacing, or co-releasing Pando with Code Storage, nor does it state that the Pierre product has been integrated into Pando. Both pieces of information appear in the same announcement context, but the specific technical relationship remains undisclosed, and Pando is not presented as a deliverable product of this acquisition.
Media Competition Framework Does Not Equal Product Launch
Axios reporter Madison Mills published a public first-line media report at 11:29 UTC on November 4, placing the same transaction in the context of competition between OpenAI and Microsoft's GitHub. The public title, byline, time, URL, and brief event summary can be used to verify the event and publication time; this article does not use the media article's main text or images. OpenAI's official announcement discusses Git workflow, source code control, and Codex, but does not announce a GitHub replacement product, so the media's competition framework cannot be written as OpenAI's already announced product positioning.
The currently confirmed scope is: OpenAI has announced plans to acquire Pierre, Codex has already used Trees and Diffs, the company plans to integrate Code Storage functionality after the transaction, and it promises that the Pierre open-source project will remain open-source. The parts that cannot be confirmed include the transaction price, closing time, regulatory jurisdiction, personnel arrangements, customer migration details, and product launch schedule. Both parties will continue to operate independently before the closing. If the transaction is not completed, these plans cannot be described as already implemented; the announcement does not provide market share, financial impact, or information about the launch of a product directly competing with GitHub.