2026. 6. 30. · 00:14
Manus social media digest — June 29, 2026
June 29's visible Manus chatter had no new official launch; the day split between Reddit builder showcases, X tool-stack mentions, and recurring support-risk complaints about browser tasks, credits, and domain porting.
June 29 signal: no launch, plenty of operating friction
This issue covers public Manus-related posts visible on X and Reddit from June 29, 2026, 00:00 to 24:00 in the channel timezone. The latest visible main @ManusAI post remained the June 24 hosting-modes announcement, so the day did not bring a new official product launch in the sampled window.1
The conversation was small but useful: Reddit showed one concrete builder showcase and one domain-porting complaint, while X mixed tool-stack mentions with direct support frustration.
The highest-signal posts
| Signal | Source | What happened | Read |
|---|---|---|---|
| Builder proof | Reddit user AyBello, whose public background was not disclosed, posted two sites they said were built with Manus: afropuppyyoga.ca and echeloninstitute.ca. The post carried a "Made with Manus" flair, 5 score, and 9 comments when read.2 | The useful part was not the title. In the comments, another user asked for more workflow detail; the author replied that Manus built "the website and all their functionalities" and later described the work as an ongoing session with "lots" of prompts.2 | This is a live-site adoption signal, but it still lacks enough detail to judge quality, prompt strategy, or how much manual repair was needed. |
| Domain and billing risk | Reddit user ApartAd5591, whose public background was not disclosed, said they had been trying for nearly half a year to port out a domain bought on Manus; the thread had a "Bugs" flair, score 2, and 6 comments when read.3 | The comments added two different signals: one user repeated a credit-refund complaint, while a community responder asked the original poster to update details in DM so they could follow up.3 | Domain transfer complaints are higher-risk than generic annoyance because they affect exit and continuity for live sites. Treat the claim as unverified user testimony unless Manus responds publicly. |
| X support frustration | X user marktomarket, a digital-advertising professional by profile, asked whether anyone had completed browser-related work with @ManusAI and called it "probably the most useless ai agent."4 X user Javeed said a $20 basic plan ran out within an hour and complained about waiting for daily credits to refresh.5 | Two other low-engagement posts asked for a company contact or accused Manus of being a scam.67 | The posts are not proof of service failure, but the repeated shape is familiar: browser reliability, credits, and response time. |
| Power-user praise with a caveat | Daniel Oon, listed on X as VP of Ecosystem at StraitsX and previously at Polygon, Algorand, Tezos, and Deloitte, said he still considered "@ManusAI 1.6 Max" one of the best business tools, while also calling its pricing "incredibly opaque."8 | The post framed Manus as useful for front-office work, not as a general consumer toy. It also paired praise with a pricing concern. | This is the cleanest positive signal of the day because it names a use context and a limitation in the same post. |
| Ecosystem and tool-stack mentions | COTI Foundation said its AI Agent Skills work with Claude, OpenAI Codex, OpenClaw, Hermes, and Manus, describing 8 skills and 48+ MCP tools.9 Tauhid IQ, an AI-builder profile, listed Manus under "AI agent workflows" in a current AI stack.10 Tabassum Parveen listed Manus as the "AI Agents" item in a 2026 AI creator stack post that drew 23 likes, 11 replies, and 711 views when read.11 | These posts do not confirm deep usage. They show that Manus is still being slotted into public AI-agent and creator-tool lists. | Good for awareness, weaker for product truth. |
Sentiment read
The day leaned toward operational trust rather than feature excitement. Positive posts treated Manus as a usable workflow tool or a member of the broader agent stack. Negative posts were more concrete: credits, domain portability, browser work, and response time.
One X complaint also repeated a "Meta dumped them" framing.4 No primary source appeared in this scan to substantiate that claim, so it should be treated as unverified social framing, not as a confirmed company event.
What to watch next
- Whether Manus answers the Reddit domain-porting complaint publicly, because domain portability is a stronger trust signal than ordinary support friction.
- Whether more users report the same credit-refresh pattern described by Javeed, or whether it remains a one-off account-level complaint.5
- Whether builder showcases start including repeatable workflows. The AyBello thread had useful curiosity in the comments, but the current evidence still stops at "lots" of prompts and an ongoing session.2
이 콘텐츠를 둘러싼 관점이나 맥락을 계속 보강해 보세요.