Meta–Manus: the cancellation order and the return to independence
The transaction involved an AI agent company. Later primary notices document a separation and effects on some users, rather than an XR procurement story.
AI-assisted, source-linked analysis. Product testing is only claimed when explicitly documented. How we work.
China's April 2026 decision against Meta's acquisition of Manus was an instruction to unwind an acquisition, not merely a warning that an unsigned purchase might fail. The subsequent company record also matters: Manus announced its return to independent operations in September. An explanation frozen at April would miss that later milestone.
The story concerns a general-purpose AI agent company. The earlier version of this article drifted into a guide to buying motion-capture gloves, hand-tracking sensors and XR hardware. Those products were not the subject of the identified acquisition. That confusion made its procurement prescriptions an unreliable account of the event.
The acquisition and the order are separate dated records
In its announcement of joining Meta, Manus described an agent intended to perform research, automation and complex tasks. It said the subscription service would continue and the company would operate from Singapore. Those were company commitments at the time, rather than a guarantee that later regulatory action could not alter operations.
The Chinese foreign-investment security-review office's April 27 notice, published by the National Development and Reform Commission, says it prohibited the foreign investment in the Manus project and required the parties to cancel the acquisition. The short notice establishes that decision; it does not publish a comprehensive explanation of every technical or commercial consideration behind it.
An order to cancel and completion of a separation are different events. The first does not, without further records, describe exactly when teams, systems, contracts or user data were disentangled. The later company announcements therefore add evidence that the April notice alone cannot provide.
Why the April reporting focused on Singapore
Ars Technica's April 27 report described the founders' Chinese origins, the move of much of the team to Singapore and integration with Meta. It explained Manus as an agentic layer coordinating tasks using underlying models, rather than an XR hardware manufacturer.
The report's discussion of relocation raises a narrower question than the earlier article's universal China-exposure scorecard. A company's headquarters, historical development work, people, ownership and transactions are different facts. Changing one does not logically establish what every authority will conclude about all the others.
This case does not supply a statistical probability of rejection for another deal. Nor does it establish a median approval time, an inevitable result for a particular nationality or an automatic rule applying to every supplier with Chinese customers. Those claims would require evidence beyond one transaction.
The August notice documents a concrete user consequence
In its August 11 note to users, Manus said its separation and regulatory requirements in specific jurisdictions required deletion of certain users' data generated on or after December 29, 2025. It described a backup window before deletion on August 23–24, Singapore time, and restoration beginning August 25.
The company distinguished affected from unaffected accounts and said the measure was not caused by a security incident. These are its descriptions of scope and cause. They do not establish that every user was affected, that every backup succeeded or that UnliveNews independently verified deletion across its infrastructure.
The dates are historical. This article is not telling readers that the August backup deadline is still open. A dated transition notice cannot safely be repackaged as a current instruction to use a process whose relevant window has passed.
September provides a later operational milestone
In its September 1 announcement, Manus said it had formally resumed independent operations under its founding team. It acknowledged the extra work and temporary interruption experienced by some users during backup and restoration.
That statement updates the April uncertainty with a company-reported operational outcome. It is not a substitute for a complete legal closing file, an independent service audit or proof that every integration with Meta was unwound in the same way. The evidence supports the milestone stated, without requiring those additional assumptions.
What this case establishes about continuity
The sequence shows why ownership announcements and product-continuity statements need dates and attribution. A promise to keep a service operating in December, a regulatory instruction in April and a data-migration notice in August address different stages. They can be read together without pretending any one document anticipated every later event.
The earlier article's compulsory vendor substitutions, six-month restructuring clock, invented approval ranges, percentage-based legal budgets and contract-clause recipes are removed. They were not supported by these records and confused a transaction account with personalized procurement and legal advice.
The supported conclusion is concrete: this AI-agent acquisition encountered a cancellation order, and later company notices described a separation with account-level consequences before a return to independent operation. That is sufficient reason to examine the actual records of a technology transition, without converting the case into an unsupported rule for every cross-border AI business.