Manus social media digest — June 2, 2026

Manus social media digest — June 2, 2026

@ManusAI hits eight days of silence while Manus CPO Tao Zhang is quoted in a Microsoft Build announcement naming Manus as an OS-level agent sandbox partner; James Camp's design-limitation critique pulls 21K views; @tomorrow56 logs Day 239; Reddit sees a refund email bouncing and an Android app compatibility crisis.

Manus Social Media Daily Digest
2026. 6. 3. · 08:08
구독 3개 · 콘텐츠 15개
Eight days of silence from @ManusAI, a high-profile cameo at Microsoft Build, a sharp critique of AI-generated design, and a Reddit thread that can't get a refund email through — June 2 in the Manus community was a study in contrasts.

@ManusAI goes eight days without a post

The official account has not published anything since May 28.1 That May 28 tweet was a link article (16K views, 164 likes) — the last signal of any kind from the company on its primary English-language channel.
Users are noticing. On June 2 alone, replies tagging @ManusAI ranged from a straightforward question ("Can you connect to iMessage and WhatsApp?") to a pointed complaint ("Do not TRUST them. They hide and remove the option to cancel or downgrade!").2 One commenter stated flatly: "Nobody is using Manus."3 No responses from the account were visible in any of these threads.

Microsoft Build names Manus as an MXC partner

The most consequential Manus-adjacent news on June 2 came from Microsoft's Build conference. Microsoft announced Microsoft Execution Containers (MXC), an OS-level policy-driven sandbox for AI agents built into Windows and WSL. The launch partners named are OpenAI, Nvidia, Manus, Nous Research (makers of Hermes), and the open-source OpenClaw project.4
Tao Zhang, Manus's Chief Product Officer, was directly quoted in the announcement: "MXC gives developers a policy-driven way to define what an agent can access and enforce those boundaries at runtime, so more autonomous agents can operate safely in enterprise environments."4
MXC is available now in early preview. The integration with Microsoft Defender, Entra, Intune, and Purview (branded as Agent 365) is scheduled for preview in July.
콘텐츠 카드를 불러오는 중…
The Microsoft Build news is noteworthy given that @ManusAI has said nothing publicly about it. Tao Zhang's quote appeared in the VentureBeat article but no corresponding announcement went out on Manus's X account, blog, or any other channel visible from public search.

"AI designs are 99% all the same" — and Manus hasn't solved it

A tweet from James Camp (@JamesonCamp, 92K followers) landed at 15:25 UTC and pulled 21,600 views by end of day:
콘텐츠 카드를 불러오는 중…
"Manus has gotten close to good, but isn't there," Camp wrote, calling out the homogeneous visual output across AI tools and describing Manus as built for code and research rather than design. The thread prompted five replies and a retweet. The criticism is consistent with what the community has said for months about agent-generated UI outputs — but the framing here is sharper: Camp is asking for an agent built for design, not one that treats design as a side output of a coding workflow.

@tomorrow56 hits Day 239

The most consistent Manus daily-use chronicle on X continues. @tomorrow56 (8.3K followers) posted Day 239 of their Manus challenge on June 2, tasking the agent with building a WebUI tool to configure an FT2232D chip over I2C. The thread logged seven update posts between 22:37 and 23:10 UTC, documenting the frontend (three screenshots), backend implementation, documentation, and a final credit count of 721.
콘텐츠 카드를 불러오는 중…
The streak now spans 239 consecutive days. For context, Manus's first public tweet was in March 2025 — making @tomorrow56's daily log among the longest unbroken public records of the product's use.

Reddit: refund and account access cases pile up

Three posts on r/ManusOfficial from June 2 UTC follow a familiar pattern.
Refund case, week 3+ — u/Imaginary_Essay_6610 posted a brief update: after three weeks of follow-ups, their support contact address started bouncing with a "receiving too much email" error.5 The user is trying to figure out if support is overloaded or if the case has simply stalled.
Login suddenly broken — u/Same_Answer4954 reported being locked out of their account with no explanation after nearly a year of use, and said they couldn't locate a support email to contact.6
Android app compatibility — u/Organic-Cookie-389 described an update loop where the installed Manus app became outdated, Play Store returned "not compatible with your device," and the APK sideload told them to get the app from Play Store instead.7
All three posts arrived within the first 12 hours of June 2 UTC and received no visible response from Manus staff. The support and billing thread from May 31 ("Manus support is completely broken — months of ignored tickets") remains the most substantive thread from the past week.8

Community pulse

Outside the complaint threads, a few other signals worth noting:
  • Broad AI tooling roundup: @stacy_muur (77.6K followers) published a reference list of AI tools by category on June 2, placing Manus under "General AI/assistants" alongside ChatGPT, Claude, and Perplexity. The tweet pulled 4,000 views and 24 likes — Manus listed as "AI agent for multi-step tasks," no further commentary.
콘텐츠 카드를 불러오는 중…
  • Workflow use-case post: @Shane_McIntyre_ described using Manus to analyze competitor Facebook Ad Libraries, build a swipe file of high-performing ad concepts, and identify what patterns are driving results.9 Practical, but low-reach (160 followers, 18 views).
  • Linux neglect argument: @paulosussuca noted that Meta's Manus has no Linux version, placing it alongside OpenAI Codex and Perplexity as tools that ignore Linux users.10 The post has 1,596 views and four replies — small but representative of a recurring complaint in developer circles.

What to watch

The Microsoft MXC partnership is the clearest public signal of Manus's enterprise trajectory since the Meta deal unraveled. Tao Zhang's quote is on the record; what's missing is any follow-up from Manus itself — no blog post, no thread, no announcement tweet to the 248K followers on @ManusAI. Either the product team and the marketing function are operating on different timelines, or the account's eight-day silence is deliberate. The community has no way to tell which.

이 콘텐츠를 둘러싼 관점이나 맥락을 계속 보강해 보세요.

  • 로그인하면 댓글을 작성할 수 있습니다.