Manus social media digest — June 8, 2026

@ManusAI ends a three-day silence with a real product ship: multi-account Gmail and Google Calendar support. Reddit's support queue adds two more frustrated users, and @tomorrow56 completes Day 244 by getting Manus to build a romaji-to-kanji converter. The Tencent acquisition narrative keeps circulating in low-signal commentary.

After posting nothing since June 5, @ManusAI came back on June 8 with a concrete feature announcement.

The post picked up 22,688 views, 330 likes, 75 bookmarks, and 27 retweets — the highest Twitter engagement for an @ManusAI post in this window. A follow-up thread tweet detailed the specific use cases: coordinate meetings across multiple calendars, draft emails from the right Gmail account, manage client/team/personal workflows separately, and use the connected accounts across Manus tasks and Projects. 1

Community reaction on X split predictably. @dahulilang called it "one of those features that sounds boring but unlocks real workflows," noting that most users have 2–3 Google accounts and the constant switching was a blocker to making Manus a daily driver. 2 @melliore_stelx put it more bluntly: "Manus just removed the switching. work, personal, client, team, all in one workflow, agent chooses which account to use when taking action. that's the thing that makes agents actually usable for real professionals." 3

The less charitable take came from @loekbosman: "Average experience with manus so far: Ask it to do a rather simple thing that would have taken you 2 minutes. Watch it think for 30 minutes. Watch your $50 budget disappear. Fail without error." 4 The multi-account feature drew replies and questions about whether it extends to Meta Ads and Instagram — a product manager handle (@louiedooey, "Product @ Manus AI") stepped into the thread to clarify that Meta Ads already supports multiple accounts with one login, and asked users to specify whether they meant Meta Ads or Instagram. 5

The Japanese daily Manus challenge hit Day 244 on June 8. @tomorrow56 tasked Manus with embedding a romaji-to-AI kanji conversion feature into a custom-built editor. 6 A series of follow-up screenshots showed the task progressing through work estimation, constraints check, and implementation — finishing with a reported credit spend of 207 and a completion screenshot.

r/ManusOfficial added two posts on June 8 itself, both carrying the support-frustration theme that has defined the subreddit for the past two weeks.

u/ConversationVast8144 posted twice in rapid succession. The first complaint: ran out of credits mid-build on an Android app that needs Google Play billing integration, now stuck. 7 This user had also posted a day earlier about $80 in credits purchased through support that never appeared in their account despite multiple "credits restored" confirmations from support. 8

u/Steamwax76 posted a brief French-language complaint: "good application but very expensive." 9

The highest-scored new post in the window (score: 7) came from u/am on June 7 evening — it was still accumulating activity on June 8. The author described two rounds of support contact after an unexplained account suspension: the first agent (named "Morgan") cited "deviation from normal usage patterns" and forwarded the case; the second agent ("Jordan") requested the same data again and promised a manual review, after which the conversation was closed with no outcome. The post ends as a warning to avoid Manus entirely. 10

A separate post from u/TheRealOctaneGuy (also June 7, still generating comments) documented a different failure mode: photo substitution errors on a large website project, where Manus repeatedly replaced the wrong photos even after corrections, and appeared to forget instructions within the same session. The user noted they had 28,000 credits to spend before renewal and pushed Manus hard across three projects. 11

The Tencent acquisition story. APF Canada (Asia Pacific Foundation of Canada, ~9K followers) posted on June 8 about China ordering Meta to unwind the Manus acquisition, citing legal commentary from Elizabeth Donkervoort. 12 This is secondary commentary on the existing narrative — no new factual development. The speculative Tencent-acquires-Manus analysis (originally posted June 6 by @PhilippePauly, 21 followers) is outside the June 8 window; both posts are being flagged here as context, not as confirmed developments.

The Reid Hoffman name-collision story. Remains in low circulation. On June 5, @glitchtruth posted a viral-framed thread treating Hoffman as actually joining the AI agent Manus — this is the same confusion that has been documented in prior digests (Hoffman left Microsoft's board to join a different company called Manus, a drug-discovery startup). The thread is outside the June 8 window but shows no sign of being corrected or withdrawn. (Unverified / misleading — confirmed false in prior issues.)

@kensavage (5,756 followers) shared a telling anecdote from a Manus AI meetup "a few weeks ago": he built an AI agent live and got applause from the developer crowd, then talked to six local business owners afterward who all asked the same question — "Can AI answer my phones when I'm on a job site?" — and had no interest in agentic workflows. The post, which got modest engagement (2 likes, 48 views), ended with the observation that the gap between what agent-builders find impressive and what small business owners actually want remains wide. 13