Manus formally resumed independent operations on September 1, 2026 — completing the unwind of Meta''s December 29, 2025 acquisition. The founding team continues, public messaging says some users needed backup and restore during the transition, and the stated roadmap shifts toward agents embedded in workflows and proactive agents rather than one-off task runs.
If you lived through August''s backup deadlines, this is the post-transition chapter. If you did not, start with explainx.ai''s August guide: Manus splits from Meta — what gets deleted and how to back up.
TL;DR — what people are asking
| Question | Direct answer |
|---|---|
| What happened Sep 1? | Manus confirms independent operations are formally resumed |
| Who runs it? | Founding team continues |
| Meta status? | Acquisition unwind complete (deal had closed Dec 29, 2025) |
| User data? | Some users went through backup/restore during transition; verify in-app if you participated |
| What''s next? | Embedded workflows + proactive agents |
| Was it a breach? | No — August FAQ cited regulatory requirements, not security incident |
Timeline — from acquisition to independence
| Date | Event |
|---|---|
| Dec 29, 2025 | Meta acquisition closes |
| Aug 11, 2026 | Manus announces separation; affected-user deletion + backup windows announced |
| Aug 23–24, 2026 | Backup/restore cutoffs (SGT) for affected users — see August guide |
| Sep 1, 2026 | Manus states independent operations formally resumed |
The awkward middle — "please back up before we delete" while corporate structure unwound — is the part users felt directly. Independence day is cleaner narratively than operationally: teams that restored successfully should spot-check task ordering, artifacts, and billing, not assume byte-identical parity.
What "embedded workflows" and "proactive agents" likely mean
Manus has not shipped a full public spec sheet with this announcement, but the phrases fit industry direction:
Embedded workflows — agents that live inside CRMs, docs, ticketing, and browser tabs instead of a standalone portal. That is the same pressure driving MCP connectors, Claude Cowork-style desktop embedding, and Copilot Studio IT agents.
Proactive agents — systems that initiate work from schedules, inbox signals, or monitoring — not only respond to typed prompts. The harness question becomes permissions and blast radius, not chat UX — see agent harness guide and destructive command guards.
Manus made TIME''s 2026 AI list via founder Xiao Hong — coverage here — so the next phase will be watched as a general-agent product test, not a niche experiment.
Portability — the lesson that outlives the Meta chapter
August''s deletion boundary taught a durable rule: agent task history is an asset class without a standard export format.
Compare mature portability:
| Asset | Portable format |
|---|---|
| Files | PDF, DOCX, etc. |
| IMAP | |
| Calendar | iCal |
| Agent task history | Vendor-specific archives only |
MCP standardized how agents reach out to tools; it did not standardize the record left behind. Until interchange exists, your leverage equals the quality of the vendor''s export button — the thesis of the August Manus backup post.
Geopolitical acquisitions amplify the risk — explainx.ai flagged Meta/Manus investigations in July before August''s backup deadline. Independence reduces one class of policy shock; it does not eliminate product sunset, pricing, or feature deprecation shocks (Gemini CLI → Antigravity migration is the same user experience, different cause).
What to verify if you restored data
- Task chronology — restores that flatten timelines break audit use cases.
- Artifacts outside Manus — client deliverables should live in storage you control, not only inside task exports.
- Billing and plan tier — "welcome back" bonuses were promised in August; reconcile statements.
- OAuth sign-in paths — Apple/Facebook sign-up users often had no email on file; confirm account linkage still works.
- Integration permissions — reconnect MCP/tool auth if tokens expired during downtime.
What builders should watch next
| Signal | Why it matters |
|---|---|
| Public API / export schema | Reduces lock-in for heavy users |
| Proactive agent guardrails | Initiation without caps = incident bait |
| Embedded workflow partners | Shows where Manus bets distribution |
| Sandbox/isolation claims | General agents running browsers need real egress policy, not slogans |
Related on explainx.ai
- Manus Meta separation — backup and deletion guide (August 2026)
- China overseas AI restrictions — Meta/Manus context
- What is an agent harness?
- What is MCP?
- AI tools system prompts leaked — including Manus
- TIME100 AI 2026 — Manus founder listed
- Google Cloud agent sandbox egress lessons
- Destructive command guard for coding agents
Official source: Manus public statements and A Note to Our Users (August 2026 transition); September 1, 2026 independent-operations confirmation via company channels.
Independence status, roadmap phrases, and transition details reflect Manus public communications as of September 1, 2026. Backup eligibility, restore fidelity, and feature availability may differ by account — verify in-app and with Manus support for authoritative status.