Manus social media digest - July 15, 2026: Support replies surface without public resolution

Bottom line

The July 15, 2026 scan window (00:00–24:00, UTC+8) produced no new standalone product post from the main @ManusAI account. The clearest fresh signal was a same-day burst of public replies from Chen_cjcj, an account that describes itself as supporting @ManusAI and @Meta. The replies show visible triage and escalation language, but no public confirmation that a refund, credit adjustment, or technical fix was completed. 1 2

Fresh X signal: public triage, private outcomes

Between roughly 2:50 p.m. and 5:40 p.m. local time, Chen_cjcj posted eight visible replies to users who had tagged Manus-related accounts. The profile describes the account as supporting @ManusAI and @Meta, and carries a verified marker, but the fetched profile data does not establish that it is an official company account. 3 4

The public pattern was consistent:

Several replies asked users to send a registered email address, a public task link, or a relevant session link so the case could be reviewed. 5 3
Other replies said that next steps had been sent by direct message. One told a user who said their frustration remained unresolved that refund requests could be submitted through support@manus.im. 6 7
The final visible reply in the burst said the case would be personally escalated to an internal team and requested the account email plus a session link. 8

That is a change in the public support surface: users were receiving named, case-specific replies instead of only posting unresolved complaints. It is not evidence of resolution. The relevant refunds, account details, and internal follow-up were directed into DMs, so the public record does not show whether money or credits were returned, or whether the underlying product issue was fixed.

Reddit checkpoint

The visible r/ManusOfficial scan is partial. Among the results clearly inside this window, one low-engagement Portuguese-language discussion post appeared at about 12:16 a.m. local time. A user with no public background disclosed wrote that they asked Manus to make a slide persuading their brother to let them play GTA V, then joked that the generated slide included details about the brother’s bad helicopter driving and the user crashing cars. The post had a score of 1 and no comments. 9

It is a small anecdote, not a reliable privacy or capability finding. With no comments and no English-language discussion attached, it does not support a broader sentiment read for the day.

Rumor checkpoint

Two third-party X posts also re-amplified the claim that Tencent could become Manus’s largest shareholder after Meta’s acquisition is unwound. Future-is-good provides little public profile context beyond a link; Emmanuel Vivier identifies himself as a HUB Institute co-founder and AI speaker. Both posts point to the same July 10 Reuters report. 10 11

This remains an unconfirmed narrative, not a completed transaction. Reuters reported that Tencent was in talks to become Manus’s largest shareholder and did not confirm a closing; the article also says the involved companies and investors had not immediately responded to requests for comment. The July 15 posts add circulation, not a new primary fact. 12

What changed today

The day’s usable signal is narrower than a feature launch: a support-looking account made several public attempts to move active cases toward email, task links, DMs, and escalation. That makes support activity more visible, while the outcome remains unobservable in public. The main @ManusAI account’s latest visible product post was still the PowerPoint update published before this window, and the visible Reddit results did not add a substantive English-language discussion.