Manus social media digest — June 12, 2026

June 12 brought a focused wave of community anxiety. @ManusAI posted nothing for a fourth consecutive day while r/ManusOfficial recorded eight new threads — the bulk of them support failures, exit planning, and an unusually detailed domain-ownership warning. The one official signal came from a replay of Thursday's three-webinar announcement still drawing organic replies. On Twitter, the Meta/Manus unwinding narrative kept spreading in Chinese and Japanese, and @tomorrow56 hit Day 248 of the daily challenge with a notably bumpy weekly AI-report run.

Official channel: silent for a fourth day, June webinars still circulating

@ManusAI did not post on June 12. 1 The team's most recent activity remains Thursday's announcement of three June webinars: Manus × SimilarWeb, Manus 101, and a session on building websites and mobile apps. 2 That tweet sat at 15,693 views with 142 likes and 34 bookmarks — its engagement is real, but so far the replies are dominated by what appears to be engagement-farm accounts rather than organic community discussion.

The context for that silence is not opaque: Bloomberg reported June 11 that Meta has severed Manus's data access and is executing the unwind of its $2 billion acquisition under pressure from Chinese regulators. 3 No statement from @ManusAI has addressed this directly.

Reddit: eight posts, seven of them complaints

r/ManusOfficial logged eight new threads during June 12 (UTC). One was a genuine positive surprise. The rest documented support breakdowns, billing issues, and what some users are now treating as a slow-motion platform exit.

The exit-planning thread

u/TheRealOctaneGuy opened the day's most-discussed thread with a practical question: what should users do now that Meta appears to be reversing the acquisition? 4 The post describes actively backing up files to GitHub, dumping database contents to a NAS, and asking Manus to generate "documents for future upgrades so I have a path forward possibly with a different agent." The framing is striking: not "should I leave?" but "how much time do I have?" The user writes they are "concerned, disappointed, and sad" about projects that were "just starting to get some traction."

Loading content card…

Domain ownership PSA

A separate post by u/Rddttrnt is the most forensically detailed item of the day. 5 The user built a small SaaS, bought a domain through Manus's website builder in April ("Buy Your Domain Instantly"), and got a few hundred users on it. When attempting to migrate elsewhere, they found:

The domain was registered to Butterfly Effect Pte. Ltd. (Manus's Singapore entity), not to the user
The registrar is Global Domain Group LLC (ICANN ID 3956), whose published abuse-contact phone number is +1.0000000
After ~a week of requesting a transfer authorization (EPP) code, the code Manus provided was rejected by three different registrars as "invalid authorization key"
Support is "a rotating cast of AI agents with no shared memory of the ticket" — one bot looked up the wrong domain entirely and told the user it had "already been transferred out"

The user has since filed an ICANN transfer complaint, escalated to the .bot registry operator (Amazon), and opened consumer-protection complaints in Singapore. The post's advice: check WHOIS on the day you buy any domain inside a website builder. "If the registrant isn't you, you don't own the domain."

Support loop complaints

Three additional posts describe the same structural pattern — an issue that never reaches a human:

u/Inevitable-Sea-4018: stuck task for weeks, AI support agent loops "refer to technical team → no reply → loop again → tried to close the case" 6
u/Icy-Rough-777: 31 emails and 8 AI bots over a code issue where Manus "effectively broke my entire site." The post ends: "Manus is cooked." The user says they have already left and are watching out of curiosity. 7
u/WalkMission3484: two posts trying to trigger a refund from kr-support@manus.ai with no response, including the full invoice number and account ID posted publicly in the hope of getting attention 8

Migration difficulty

u/Unusual_Archer9443 described trying to migrate a web app from Manus to Vercel. 9 Each refactoring attempt leaves Manus dependencies in the code; credits run out in the correction loop. The user notes they "know nothing about coding either" — meaning the intended non-developer audience has no fallback. Given the domain PSA above, the pattern of lock-in extends from hosting to domains.

Bright spot: pixel art over-delivery

u/Content_Leader_5922's final post of the day gave the community something different: they asked Manus to draw a 32-bit tree on a pixel art site, expected a "brown dot with a green cube," and got something considerably more detailed. 10 The post ended with the observation that this task burned all the free credits on the account — an accurate summary of the current Manus experience in miniature.

Twitter: acquisition commentary keeps circulating, Day 248 hits a task error

The @ManusAI account's silence on June 12 did not slow down the Meta/Manus conversation. Several Chinese- and Japanese-language threads continued to spread the acquisition-unwind story, focusing on its geopolitical implications.

@zengying1107 (24.6K followers) posted a detailed bilingual summary at 5,180 views, describing the situation as "AI entering national-security territory" and noting that the founders are exploring raising roughly $1 billion to buy back from Meta. 11 A Japanese commentator (@mikaokuda) framed it as the AI-industry equivalent of the TikTok sale dispute — "the first layer is now national governments, not AI platforms." 12 Both posts repeat details from Bloomberg and Reuters reporting; neither contains new primary facts.

A separate thread from @Manavvv31 ranked Manus #3 in a "Top 10 AI Tools in 2026" roundup (1,288 views, 14 retweets). 13 The description calls it "China's first general AI agent" and highlights the persistent virtual environment. The framing is flattering but already reads as a historical artifact — the entry makes no mention of the acquisition situation.

@tomorrow56 logged Day 248 of the daily Manus challenge. 14

Loading content card…

The task was a weekly AI-related report. The run generated several friction points: a one-year date-range error that needed immediate correction; Manus opting to use Wide Research mode as instructed but stalling at a Notion registration step. Two credit usage screenshots were posted — 96 and 192 credits for separate tasks. At 470 views, the day's Manus post was the highest-engagement item from @tomorrow56 in this window.

On the negative end, @SubhashChalla (38 followers) posted a public complaint — account suspended without explanation, calling Manus "3rd class AI service, waste of time." 15 Low reach, but consistent with the account-suspension pattern documented repeatedly on Reddit since early June.

Sentiment snapshot

Category	Signal count	Tone
Support / billing failure (Reddit)	5 posts	Negative
Exit planning / platform migration	2 posts	Concerned
Meta/China acquisition commentary (X)	4+ threads	Analytical
Positive product experience	1 post	Positive
Daily challenge (@tomorrow56)	1 series	Mixed
Official @ManusAI posts	0	—

The day's ratio is consistent with the past week: genuine product curiosity exists, but the public record on June 12 is mostly a support-failure queue and a platform-stability concern rippling out from the Bloomberg report. The domain PSA is the single most actionable item — any user who bought a domain through Manus's website builder should verify WHOIS registrant status immediately.