Manus social media digest — June 3, 2026
@ManusAI breaks a 6-day silence with a new post; Reddit sees three domain and billing escalations in one day including an ICANN complaint; an OpenCLI developer files a manus.im adapter request; and @tomorrow56 skips Day 240 for the first time.
@ManusAI breaks its six-day silence with a new post; Reddit fills with three domain and billing escalations in a single day; an OpenCLI adapter request signals developer tool interest; and @tomorrow56 skips Day 240 for the first time.
@ManusAI posts again — but the content stays behind a wall
After six days of silence since its May 28 article post (16K views), @ManusAI published a new link post on June 3 at 14:57 UTC.1 The post points to an X Article — a format that requires a logged-in session to read in full — and reached 6,109 views, 51 likes, and 27 bookmarks within hours, modest by the account's recent standards. The account's bio still reads "Manus from @Meta," unchanged since the NDRC-ordered Meta deal unwind first surfaced in late May.
Loading content card…
The return to posting ends the longest stretch of official silence this channel has tracked (6 full days vs. the previous record of 4). Whether this marks a resumption of regular cadence or a one-off remains to be seen — the post itself provides no context.
Reddit: three escalations, one day
The three Reddit posts filed on June 3 share a common structure: a user who trusted Manus for something production-adjacent, hit a wall, attempted every official support channel, and got either an AI loop or nothing.
Domain transfers reach ICANN. u/Ok_Ask4144 raised a formal ICANN domain transfer complaint after four unanswered requests for the auth-code needed to move a domain from Manus to GoDaddy — a step that cannot be done via the dashboard.2 Every response was an AI reply. In a separate post the same day, u/Rddttrnt issued a similar domain-hosting warning and said they are trying to get an EPP code to migrate off, adding: "Pity a great project became too big, then stopped supporting clients, and is doomed to fail soon."3
38,000-credit deduction labeled "refund." u/Ashamed_Ad_6973 reported waking up to a 38K credit deduction during a routine web coding and document research session, with the transaction labeled "refund" — no explanation provided.4 Multiple emails got no meaningful reply; two days before filing the Reddit post, a support bot closed the ticket citing "session too long." The user had purchased a large credit package and is asking the Manus team to make direct contact.
Loading content card…
These three posts join a pattern that has been building over the past two weeks on r/ManusOfficial: the subreddit has become, as u/Rddttrnt put it, a place where "most of posts... is warning others." The refund saga of u/Imaginary_Essay_6610 entered a new chapter the same week: after three weeks of follow-ups, the user's support emails began bouncing with a "recipient receiving too much email" delivery notice — a possible indication that the support inbox is overwhelmed rather than simply slow.5
Twitter: "Chief of Staff" framing, a locked-out Pro Max user, and developer tooling
Framing shift noted. @mikemichelin observed that Manus has started positioning itself as a "Chief of Staff" rather than an "assistant," and reads this as a deliberate response to OpenClaw's arrival — "an assistant waits for instructions; a Chief of Staff coordinates, delegates, and surfaces the things you didn't think to ask for."6 The tweet has minimal reach on its own, but the framing distinction is the kind of positioning debate that tends to recur as the agent category matures.
Pro Max user locked out for 9 days. @JPeaco (Founder & CEO, ~1,900 followers) tagged @ManusAI publicly: after a company rebrand, his old email won't log in and the new email is treated as a separate account. After 9 days, 3 emails, and support chat that "just loops to help articles," he is asking for direct intervention.7 A Pro Max subscription at £168 for 2 seats is at stake.
Competitor comparison. @brandon_galang (3,289 followers, Applied AI at Vercel) reviewed Airtable's new Hyperagent and called it "the first agent I've seen to attempt user-facing control loops around self-learning and evals," then framed it as "like a pro version of @ManusAI."8 The comparison positions Manus as the baseline reference for consumer-grade autonomous agents — a compliment and a competitive marker at the same time.
Developer tool integration requested. A GitHub user filed issue #1836 on the OpenCLI project requesting a manus.im adapter.9 The proposal maps Manus task submission and status polling to OpenCLI's existing patterns (similar to existing Kimi and Codex adapters), with read-only commands (
manus list, manus read, manus status) and state-changing commands (manus new-task --yes, manus pause/resume/cancel). The request is unverified as proceeding, but it is a concrete signal of developer interest in treating Manus as a CLI-accessible agent backend.Loading content card…
@tomorrow56 skips Day 240
For the first time in this channel's tracking history, @tomorrow56 posted that they would skip the Manus daily challenge due to an emergency.10 The day's tweets shifted to Windsurf (now rebranded as Devin Desktop), with notes on the GUI change and task history disappearing after a Windsurf session. No Manus usage logged; no credit count for Day 240.
What to watch
- Whether @ManusAI's June 3 post is the start of a resumed posting cadence or a one-off.
- Manus team response (or non-response) to the ICANN transfer complaint — domain portability is a legally bounded issue with deadlines.
- Whether the OpenCLI adapter request moves to a PR or stalls; it would be the first documented CLI-layer integration for Manus.
- @tomorrow56's return: whether Day 241 resumes, and whether they stick with Manus or shift to Devin Desktop.
References
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.