Manus social media digest — June 25, 2026

June 25 was not a product-launch day for Manus on the main account. The useful signal came from users instead: a Reddit refund complaint that appears to have been resolved after a community reply, a late-day personal task-manager build, and several low-engagement X posts that split between praise and operational frustration.

Coverage note: this digest covers visible English-language X/Twitter and Reddit activity published during June 25, 2026 in the channel timezone. Reddit coverage is based on visible r/ManusOfficial results rather than a full Reddit crawl. User complaints are treated as unverified testimony unless Manus or a clearly attributable support account responded in public.

What changed today

Signal	What happened	Confidence
Main @ManusAI account	No newer visible main-account post landed inside the June 25 local window. The latest visible post remained the June 24 23:59 local hosting-modes announcement, one minute before this issue's cutoff. It described Autoscale for idle sites and Reserved hosting for always-awake apps. 1	High for the scan; the cutoff matters.
Reddit support risk	A Reddit user said they accidentally bought a $2,000 yearly Pro plan, received a chatbot message saying the refund had been processed, then still saw the subscription as active. 2	Unverified user testimony, later publicly marked resolved by the poster.
Reddit builder signal	A r/ManusOfficial user published NewRowList, a personal task manager built after asking Manus for a simple web app to capture same-day tasks, history, priority, notes, calendar sharing, subtasks, projects, and weekly progress summaries. 3	First-person build story; no public comment discussion at capture.
X sentiment	X was low-volume. The strongest posts were not viral, but they were concrete: production-hosting complaints, customer-support complaints, first-use praise, and creator/workflow examples.	Moderate; useful as weak signal, not as market consensus.

Support and reliability were the loudest risk signal

The most concrete support thread came from Reddit. The poster, whose public background was not disclosed beyond the Reddit username, said the Manus support chatbot told them a refund had been processed for an accidental $2,000 yearly Pro purchase. The post included a transcript dated June 25 at 11:09-11:42 Singapore time, then said the subscription still appeared active and that the user could not reach human support. 2

The public follow-up matters. A commenter said they had experienced the same issue but did receive a refund; another user, u/HW_ice, replied that the refund had been processed and asked the poster to check their inbox. 4 The original poster then replied, "Yep, this issue is resolved by u/HW_ice." 5

That makes the thread different from a raw complaint: it still points to a bad support handoff, but it also shows visible intervention after the post went public.

Loading content card…

X produced a separate reliability complaint from Zulfiqar Ahmed, a verified X user whose bio emphasizes sustainability, energy, innovation, and governance. He said two production apps built and hosted on Manus had been down for nearly three weeks, with tickets raised, automated replies received, and no resolution. 6 Treat this as unverified user testimony. It is still higher-risk than a generic dislike post because it concerns hosted production apps.

Loading content card…

A second X complaint came from Eric Protic, whose bio identifies him as founder of SuperConnect Data and co-founder of Bay-Harbor Marine Services. He described a two-day support loop and said he could not reach a real person or get an ongoing issue fixed. 7 A separate verified account named Chen, with a bio saying "Supporting @ManusAI @Meta," publicly replied to another refund-related inquiry by asking for the account email via DM and saying the case would be escalated. 8 That reply suggests some public support triage was happening, but it is not the same as a main @ManusAI product or policy statement.

Builder posts still show why people tolerate the rough edges

The day also had a useful counterweight: people are still using Manus as a practical app builder, not just talking about it as a general AI category.

The strongest Reddit build post was "Manus Organizes My Brain." The author described themselves in the post as a small manufacturer, distributor, service provider, and inventor. They said they asked Manus to build a simple todo-style web app because notes disappeared from view and calendar tools did not capture what they needed "right now and today." 3

The post said Manus first asked clarifying questions, created an early version in minutes, and then iterated through voice transcription fixes, outcome notes for finished tasks, logo creation, priorities, inline editing, multi-user sharing, iCal pushes, weekly summaries, subtasks, projects, ordering, and mobile/tablet/laptop troubleshooting. 3 There were no comments returned for the thread at capture, so this is best read as a first-person showcase rather than a community-tested build.

Loading content card…

On X, a verified Singapore-based user posting as bling said a first Manus session felt stronger than other platforms and listed digital colleagues, multi-agent orchestration, deep research, broader real-world use, and concurrent task workflows as the things that stood out. 9 Ninja, an X user whose bio says "Content creator" and "All in @SeismicSys," said they created a website on Base from Discord FAQ material and found Manus "a little bit different" from tools such as Replit. 10

These posts are small, but they are consistent with the same pattern seen in recent Reddit showcase posts: Manus earns praise when it turns messy personal or domain-specific context into a working artifact. It gets punished when that artifact becomes a dependency and support, hosting, credits, or billing feel hard to verify.

Ecosystem signal: Semrush surfaced as a use case, not a confirmed product update

One late X reply tagged both @ManusAI and @semrush and said, "finally, semrush data i can actually use without opening 14 tabs." 11 The author, Samian, describes himself as a full-time software engineer building agent-style testing tools. The post is a weak but relevant use-case signal: people are talking about Manus in the context of turning SEO data into usable workflow output.

It should not be treated as confirmation of a durable Manus-Semrush integration. The post is a reply, not a Manus announcement, and the main @ManusAI timeline did not publish a corresponding June 25 product note inside the scan window. 1

Sentiment read

The day's visible chatter splits into three buckets:

Operational trust: Refunds, support loops, and hosted-app downtime were the sharpest negative signals. One Reddit refund case appears resolved in public, but the original complaint still shows that users can become worried when an AI support agent claims completion before the user can verify it.
Builder utility: The NewRowList, Base website, and first-use praise posts all point to the same appeal: Manus is valued when it converts personal context into a working app or workflow.
Official quiet: With no new main @ManusAI post inside the June 25 window, the official narrative did not redirect the conversation. The latest visible official post remained the hosting-modes update just before the window opened. 1

Bottom line: June 25 was a trust-and-utility day. The positive stories were about what Manus can build. The negative stories were about what happens after users depend on what it built.

What changed today

Support and reliability were the loudest risk signal

Builder posts still show why people tolerate the rough edges

Ecosystem signal: Semrush surfaced as a use case, not a confirmed product update

Sentiment read

References