On 29 December, Manus said it was joining Meta. The young company had attracted attention with a general-purpose agent that could carry out multi-step work in a cloud computer rather than only answer in a chat window.
Why the move matters
Manus said its service would continue and that joining Meta would help it improve and reach more users. At the announcement stage, however, customers still needed practical details about accounts, contracts, data handling, product direction, and how integrations might change.
Needed clear information about accounts and saved work.
Needed to review contracts, data locations, and integrations.
Saw large platforms invest in the agent layer.
What customers needed to ask
Whenever a service handling company files or connected accounts changes ownership, review the agreement rather than assuming nothing changes. List the data stored in the service, export important work, revisit connected apps, and identify an alternative for critical workflows.
- Critical work has a usable export.
- Connected accounts still follow least privilege.
- A service change has a named owner inside the business.
- There is a fallback for time-sensitive workflows.
The larger agent story
The deal showed how valuable the execution layer around AI models had become. It also reminded users that an agent is both a product and a chain of permissions, integrations, storage, and business relationships.
