Manus social media digest — June 7, 2026

A quiet Sunday from @ManusAI on X — no new post for the second consecutive day — while r/ManusOfficial logged six new threads that together sketch a community split between frustrated departures and users still in the middle of active projects. The most telling signal: a "Manus vs Claude" thread drew responses that tilted sharply negative, but one long-form reliability post still opened with "Manus is still helping me get a ton of work done."

@ManusAI posted nothing on June 7.1 Its June 5 paywalled X article (tweet ID 2062913499869909351) climbed to 9,434 views by the end of the day, up from 8,391 the previous morning — steady long-tail engagement on a post that requires an X subscription to read in full.2

The account's pattern since June 3 has been one paywalled X article every few days, no community engagement in replies, no new product announcements.

The Manus vs Claude comparison thread opened with a simple question and drew eight replies within the day.3 The breakdown:

The vote spread was 4 upvotes for the question, with no single reply clearly winning the thread — which itself says something about where community consensus is (or isn't) right now.

The reliability cracking post is the most substantive June 7 entry.4 The author, who had 28,000 credits to spend before renewal, was working on three major projects over three days and kept running into the same failure loop: Manus replaces the wrong photos despite explicit instructions, acknowledges the mistake, attempts to fix it, fails again. By the end the agent was contradicting advice it had given two steps earlier and arguing against ideas it had previously recommended. The post is framed as an observation, not an ultimatum — "Manus almost feels bi-polar. It's wild" — but it documents something systematic rather than a one-off bad session.

Two account suspension threads landed within hours of each other in the evening.

The first, titled "Account suspended — no explanation, conversation closed twice — bye bye," describes the now-familiar playbook: account flagged for "deviating from normal usage patterns" (testing slide creation and research), two separate support contacts that each ended with an automated "conversation closed" message, no actual review visible to the user.5 The poster was done with Manus and said so plainly.

The second was a developer who's locked into a one-year subscription and is building a VS Code extension to route messages to Manus through the editor.6 The question — will this get my account banned? — landed in a context where the suspension track record makes it a reasonable thing to worry about before building something useful.

Two billing threads rounded out the day.

One user spent $80 on credit upgrades, was told by support four or five times that credits had been restored, and still saw nothing in the account — blocking a Google Play app launch.7 Another reported free credits not appearing at the expected time after the timer shifted from 12:30 to 03:25 with no explanation.8

Tencent acquisition speculation (@PhilippePauly, 20 followers, ~62 views): a detailed thread arguing that a Tencent rescue of Manus is "highly probable" given State Council Order No. 837 and the blocked Meta deal.9 The argument is internally structured but rests entirely on inference — no sourcing, no named parties, no corroboration. Unverified.

Reid Hoffman / Manus name confusion continues to circulate in low-follower accounts.10 As noted in prior digests: TechCrunch's June 5 article referred to Manas AI (manasai.co), a drug-discovery startup — not manus.im. The two companies are unrelated. Hoffman has no known affiliation with manus.im.

@tomorrow56 posted his weekly note.com semiconductor report on June 7 and several Japanese-language personal finance / tech-writing threads.11 No Manus daily session log for what would have been Day 242.