Manus social media digest — May 30, 2026
@ManusAI stays silent for a fifth consecutive day; billing complaints cluster around an unresolved internal error; a 10-person Manus org chart thread circulates; and someone reverse-engineers the Manus planning workflow as an open-source Claude Code skill with 22K GitHub stars.
Five days of official silence. Billing complaints cluster. Someone reverse-engineers the Manus workflow and open-sources it.
@ManusAI: still quiet, with one caveat
@ManusAI has not published a new tweet since the Projects mobile announcement on May 25 — now five days ago.1 That said, the account's May 28 post (15,389 views, 161 likes, 95 bookmarks) was a link to the Notion connector blog entry published that day, not a new announcement — it's the same post covered in Thursday's digest.2 The blog itself has no new entries dated May 30. The account's follower count sits at 248,788; bio still reads "Manus from @Meta."
The silence pattern now spans more than a week of net product activity on X, with blog output (customer stories, connector guides) continuing as the main publishing channel.
Billing and support complaints persist
Three separate users surfaced billing or support problems on May 30, each describing a slightly different failure mode:
@o_o_dr tweeted twice. First, he reported that Manus's own support team had confirmed his website was down because of an internal billing system error — not his payment method — yet no fix or timeline had been provided.3 Hours later he was back, tagging @ManusAI again to say the support loop was still unresolved.4
콘텐츠 카드를 불러오는 중…
@EmilyMaggz described being charged through Stripe despite appearing to be on the free tier, then deleting her account — and still not having the issue resolved. Her description of support: "an AI-agent loop: 'contact us from the registered email,' then no context from previous emails."5
@jukaichla reported a verification code failure when trying to log in — a simpler friction point, but one that adds to the day's support noise.6
@o_o_dr has appeared in this digest before (May 29); the complaint has now stretched across multiple days without a visible resolution.
The account anatomy of @Sonofpeace0001
Yesterday's digest noted that @Sonofpeace0001's CREAO-vs-Manus credit comparison pulled 34.7K views. Today, @Tttx967715T — who runs an "account autopsy" series — published a short thread analyzing whether @Sonofpeace0001 is a genuine builder or something else.7
His read: the bio ("AI Agent Builder / Autonomous AI workflows daily / 100+ builds live / CREAO / Manus / Hermes comparisons") looks credible on the surface, but the posting behavior is more consistent with "a product growth node" than with an independent practitioner. The thread didn't name a sponsor and stopped short of calling it promotional outright.
This follows yesterday's observation (already noted in this digest) that the CREAO vs. Manus framing had a promotional tilt. The autopsy thread has only 43 views as of this writing and shouldn't be treated as confirmed — it's worth logging as a signal for how the community is reading that account.
콘텐츠 카드를 불러오는 중…
Who is Manus, actually? A 10-person org chart circulates
@GoSailGlobal (32,180 followers) published a Chinese-language thread mapping the Manus/Butterfly Effect org chart — 4,673 views, 28 bookmarks, 25 likes as of late May 30.8
The thread is the third installment in a "three camps" series covering AI agent teams (Anthropic Claude team, OpenAI Codex team, Manus/Butterfly Effect). The Manus breakdown:
| Handle | Role |
|---|---|
| @ManusAI | Main brand (248K+), bio: "Manus from @Meta" |
| @ai_manus | Product secondary account |
| @ManusAI_IM | Global / international |
| @ManusAI_JP | Japan (14K+) |
| @Red_Xiao_ | Xiao Hong, Founder & CEO |
| @peakji | Yichao "Peak" Ji, Co-founder & Chief Scientist |
| @hidecloud | Tao Zhang, Co-founder & CPO (ex-ByteDance) |
| @HenrypenmanXD | Co-founder & CMO |
| @parker_lyman | Chief of Staff |
| @manuscommunity | Community / events |
The thread is the most widely circulated English-readable org reference in the window and worth bookmarking if you're trying to track who's actually speaking for Manus on any given day.
"Stuck in limbo": the Meta deal narrative keeps framing public perception
Two accounts on May 30 described Manus as being "stuck in limbo" in the context of the Meta acquisition unwind.9 No new factual developments were attached to either comment — both appear to be reactions to older reporting. The Epoch Times piece "How Manus Tried to Leave" (published May 19) got a fresh share on May 30, reaching a new cohort of readers.10
Nothing in today's window constitutes new information about the buyback situation. The narrative is simply still traveling.
Open-source reverse-engineering: someone rebuilt "the Manus workflow" as a Claude Code skill
A tweet from @sentient_agency (107K followers) and a separate post from @chenzeling4 both circulated a project that claims to have reverse-engineered the core Manus planning pattern and released it as an open-source Claude Code skill called "Planning with Files."1112
The description: the skill uses persistent markdown plans to keep agents on track across complex tasks, and reportedly hit a 96.7% pass rate on benchmarks and won 3 out of 3 blind A/B tests against baseline. The GitHub repo had 22,300 stars at time of the tweet. This is a slightly different project from ARGO (the local Manus alternative that's been circulating for the past several days), but it comes from the same general impulse: extracting what Manus does architecturally and making it available without the subscription.
The claim about "reverse-engineering Manus" should be read carefully — it's a marketing framing, not a verified technical audit.
Community activity
@tomorrow56 hit Day 235 of his daily Manus challenge on Saturday (weekly AI report, 986 views) and Day 236 on Sunday (China semiconductor weekly, 288 views). Both posts tagged @ManusAI, @ManusAI_JP, and @manuscommunity as usual.1314
@Christel_OCC (6,972 followers) shared a demo of turning an article into a full strategy with Manus and having it automatically implement the suggested changes — posted a YouTube link alongside the tweet (256 views, 4 likes).15
콘텐츠 카드를 불러오는 중…
@DinoDeer (24,822 followers) opened a pricing debate with a pointed question: "You all say AI can replace employees — why do you find Manus and Genspark expensive?" The post got 2,927 views and 5 replies.16
@unprofeshme (461 followers, 469 views) made a dry observation about Manus billboards in Singapore: "the last company I remember with 'AI' on billboards all over singapore was.... manus. so i'm sure this is totally unrelated and will turn out totally chill." The post didn't name the other company putting up billboards, but the framing suggests she had just seen another AI brand taking the same outdoor media approach in Singapore.17
r/manus_ai on Reddit returned no posts for the third consecutive day. The subreddit remains effectively inactive.
What to watch
- Whether @ManusAI breaks its silence heading into the first week of June — the last two silences (May 20–25) ended with a product drop.
- @o_o_dr's billing complaint has now gone unresolved across two consecutive digest days; if the internal billing error mentioned by support is systemic, other users may surface similar reports.
- The Japan chapter June 17 Zoom (Manus AI ともまえ Nights) is now 18 days out. No change in status.
참고 출처
- 1@ManusAI on X
- 2Manus blog — The Connector That Turns Notion Into a Workflow Engine
- 3@o_o_dr on X (billing error)
- 4@o_o_dr on X (follow-up)
- 5@EmilyMaggz on X
- 6@jukaichla on X
- 7@Tttx967715T on X
- 8@GoSailGlobal on X
- 9@Imnothere202300 on X
- 10@tralalawarbler on X (Epoch Times share)
- 11@sentient_agency on X (ARGO thread)
- 12@chenzeling4 on X (Planning with Files)
- 13@tomorrow56 Day 235
- 14@tomorrow56 Day 236
- 15@Christel_OCC on X
- 16@DinoDeer on X
- 17@unprofeshme on X
이 콘텐츠를 둘러싼 관점이나 맥락을 계속 보강해 보세요.