Manus social media digest — June 18, 2026
June 18 did not bring a new official @ManusAI feature post. Instead, X amplified a reported Meta buyback narrative while Reddit and X users described refund, domain, payment, and DNS/SSL dependency risks.
June 18 was noisy, but not because @ManusAI shipped another official update. The official account's latest visible product post in this scan remains the queued-message feature from June 16 at 23:03 UTC+8, while June 18 chatter moved toward three less comfortable themes: a reported Meta buyback narrative, user reports of production dependency risk, and Reddit complaints about refunds, domains, and whether the service is stable again 1.
This issue covers visible English-heavy X/Twitter results and r/ManusOfficial posts published during June 18 in UTC+8. Reddit coverage is based on visible subreddit results, not a full-platform crawl.
The short version
| Signal | What changed on June 18 | Confidence |
|---|---|---|
| Official channel | No new @ManusAI product post appeared in the June 18 window; the June 16 queued-message post remained the latest visible official update in the captured timeline 1. | High for the captured @ManusAI timeline; not a guarantee of every regional account. |
| Community marketing | The verified Manus Community account promoted a short film made with @ManusAI-generated images and Manus Slides image mode at 22:55 UTC+8 2. | High for the post; low engagement so far. |
| Meta unwind narrative | A late-day X post from Sheel Mohnot (@pitdesi), a verified VC account with 199k followers, said original backers were reportedly buying Manus back from Meta at the $2 billion price, and claimed revenue had risen to $400-500 million 3. | Treat as reported social commentary until primary documents or company statements appear. |
| User-risk reports | A verified user said two live apps were down because of a Manus-related DNS/SSL infrastructure failure; another verified user described account-access trouble after paying $1,500/month 4 5. | User testimony only; no official resolution found in this scan. |
| Reddit support queue | r/ManusOfficial added fresh posts about refund non-receipt, EPP/domain-transfer codes, app stability, credits, and whether AI agents are becoming interchangeable 6 7 8 9. | High for post existence; claims are unverified. |
Official product signal: quiet, but the community account pushed Slides
The official product account did not add a new June 18 update in the captured timeline. Its latest visible post remained the June 16 queued-message announcement, which had 18,819 views, 196 likes, 15 reposts, and 20 replies at capture time 1.
The new product-adjacent signal came from Manus Community, a verified account whose profile describes it as a community by @ManusAI. At 22:55 UTC+8, it posted a short film pitch: every frame was described as an image generated by @ManusAI, and the deck at the end was said to be made with Manus Slides in image mode 2. The post had only 46 views and one like in the captured detail, so it is a useful product-positioning signal rather than a broad community event.
Loading content card…
The contrast matters. Official @ManusAI stayed quiet on the main channel, while the adjacent community account tried to move attention back to creative workflows. That is a different rhythm from June 16, when the official queued-message feature itself drove the discussion.
The Meta/Manus story became a late-day X narrative again
The highest-signal English post captured in the late June 18 wave came from Sheel Mohnot (@pitdesi), a verified San Francisco VC account whose profile says he works at @btv_vc leading pre/seed rounds in fintech and vertical AI. He wrote that Manus revenue was now $400-500 million, up from $100 million at the time of acquisition, and that original backers except Benchmark were reportedly buying the company back from Meta at the $2 billion price paid 3.
Loading content card…
The important word is "reportedly". This scan did not find a Manus, Meta, regulator, or filing-level primary source inside the channel's X/Reddit evidence set. So the right read is not "deal confirmed". It is: the Meta unwind story moved from background commentary into a more detailed X narrative, with revenue and buyback numbers circulating in public posts.
For readers tracking operational risk, the relevance is simple: when public conversation frames Manus as a company being separated, repurchased, or relocated, users with live workflows become more sensitive to support, hosting, billing, and account-control failures. June 18 produced exactly those failure reports.
User-risk reports: billing, DNS/SSL, and domain control
The clearest production-dependency complaint came from Zulfiqar Ahmed, a verified X user with 50,660 followers whose profile describes sustainability, energy, innovation, and social entrepreneurship interests. He said two live apps were down because @ManusAI had a DNS/SSL infrastructure failure, adding that one app had been down since June 7, another was down that day, both showed green ticks in Manus's dashboard, and he was migrating to Railway 4.
Loading content card…
A separate X complaint from Matt Mastro, a verified account whose profile says he is the creator of PEPSTRO, said that for a second month in a row he had lost account access because of a payment-processing issue despite paying $1,500/month. He claimed that in 60 subscription days, 10-12 days were unusable, and that Chase, Stripe, Link, and Apple were not the source of the issue 5. In a follow-up, he said he had read the same support message 15 times and criticized the "internal team" handoff loop while also saying he liked what the app could do 10.
On Reddit, the complaints were lower-engagement but more numerous. One user said Manus had promised a card refund within 1-15 business days after an annual-subscription charge and credit-access problem, but that more than two weeks had passed with no refund and the support ticket closed 6. Another asked how to get EPP codes for two domains registered through Manus, saying they had been told for months that the request was escalated and that someone would contact them within 48 hours 7. A third, posted just after midnight UTC+8, said Manus had registered a domain under its own name rather than the correct company's name, leaving the company without access for redirects, transfers, or host changes 11.
These are unverified user accounts, not proven incidents. But as a pattern, they are more consequential than routine "support is slow" posts. They describe dependencies that can block a business from changing a site, moving a domain, editing a live app, or receiving a promised refund.
Reddit mood: "is it fixed?" plus agent commoditization
The day's Reddit mood was not only anger. One r/ManusOfficial user asked whether the app and website were "back to normal" after recent issues, and the post had five comments in the captured detail 8. Another asked whether AI agents are becoming interchangeable, arguing that browser automation, task planning, file handling, research workflows, and visible execution are converging across platforms 9.
That second question is worth watching even though it had little engagement. It reframes Manus's problem from "does the agent work?" to "what makes this agent meaningfully different?" If users see the category converging, then reliability, support, migrations, and pricing become bigger differentiators than demo polish.
There was one small positive use-case signal on X: Heicoders Academy said a course participant used Manus AI to build PetCare, a functioning pet-sitting platform with matching, scheduling, and payment features. The account has only 13 followers in the captured detail and the post showed four views, so it is a concrete anecdote rather than a broad trend 12.
What to watch next
- Official response cadence. If @ManusAI stays quiet while support complaints accumulate, the main account will stop anchoring the daily narrative.
- Infrastructure ownership. DNS, SSL, EPP codes, domain registration names, and database quotas are now recurring risk categories. They matter because they affect whether users can exit, migrate, or keep live products online.
- Meta buyback evidence. The X narrative now includes specific revenue and $2 billion buyback claims, but this issue treats them as unconfirmed until a primary source appears.
- Support escalation language. Several posts describe escalation to an "internal team" or a 48-hour callback with no visible resolution. If that wording keeps repeating, it becomes a support-pattern signal rather than isolated frustration.
Bottom line: June 18 did not deliver a new official Manus feature story. It delivered a dependency-risk day, with a creative Slides post on one side and a cluster of user-control complaints on the other.
References
- 1@ManusAI queued-message post
- 2Manus Community Slides short-film post
- 3Sheel Mohnot on reported Manus buyback
- 4Zulfiqar Ahmed DNS/SSL complaint
- 5Matt Mastro payment/access complaint
- 6Reddit refund complaint
- 7Reddit EPP codes post
- 8Reddit app-stability question
- 9Reddit agent-interchangeability post
- 10Matt Mastro support follow-up
- 11Reddit domain-support complaint
- 12Heicoders PetCare Manus use case
Add more perspectives or context around this Post.