Manus AI — viral Chinese agent that turned out to be Claude Sonnet + 29 tools

The Manus AI cycle of March 2025 is the cleanest case study in 2025’s viral-AI-product economics. On March 7, a Chinese startup called Manus launched a general-purpose AI agent with a launch video showing it autonomously completing complex multi-step tasks — research, file manipulation, web automation, code generation. The Reddit reaction was immediate and outsized: an r/singularity thread (856 upvotes) framed it as “the next DeepSeek moment.” Multiple subreddits hit 1000+ upvotes within 48 hours.

Then, on March 10, an r/LocalLLaMA thread (447 upvotes) — “Manus turns out to be just Claude Sonnet + 29 other tools, Reflection 70B vibes ngl” — reverse-engineered the demo. The reveal: Manus wasn’t a new model. It was Claude Sonnet 3.5 with a tool harness around it. The system prompt and tool list leaked; the architecture was a standard agent loop with external tool calls.

The story isn’t “Manus was a scam.” The story is what the hype-then-reveal cycle says about where the AI industry is in March 2025, and how engineers should evaluate the next “DeepSeek-shaped” launch.

What Manus actually did

The demo videos were genuinely impressive. Manus could:

• Take a research request and produce a multi-page report with citations
• Automate browser-based workflows (filling forms, scraping data, navigating apps)
• Execute multi-step file operations (download data, transform it, output a result)
• Generate working code for medium-complexity tasks
• Coordinate across multiple specialized “sub-agents” for different parts of a task

The presentation framing: this is a Chinese company’s answer to OpenAI’s then-rumored agentic products, leapfrogging American labs. Limited-invite access. Mystery around the underlying tech. Long waiting list. Classic viral-product playbook.

What Manus turned out to be

Within days, community sleuthing produced the reveal:

• The underlying model is Claude Sonnet 3.5 (Anthropic’s hosted API)
• The agent loop is a standard ReAct-style harness with 29 tools wired up
• The tools include: browser automation, file I/O, code execution sandbox, web search, database queries, image generation, audio processing, and others
• The system prompt was leaked and shows a fairly conventional agent-orchestration prompt structure

From the r/LocalLLaMA top comments (370+ upvotes):

“I asked claude how I can create a startup and get it valued at a few billion dollars over the weekend by using clever marketing and after thinking for 2 seconds it told me [exactly this playbook].”

“The amount of hype in this space is unreal. Make a sped-up demo video, release on YouTube, your startup gets a billion dollar valuation.”

“What did people think it was? I assumed it was just a bunch of tool calls cobbled together.”

The dissent within the dissent: “just Claude + tools” is itself non-trivial. Building a reliable agent harness with 29 tools, prompts that coordinate them well, and a demo-worthy output is real engineering. The community’s “it’s just X” framing undersells the orchestration work.

But the original framing — “next DeepSeek moment, Chinese AI breakthrough” — was clearly wrong. The breakthrough, such as it was, was orchestration and demo production, not novel modeling.

What the cycle says about March 2025

Three patterns crystallized:

1. Agent harnesses are now the productization layer for frontier models. Manus, Devin (Cognition Labs), Replit Agent — they’re all the same architecture pattern: frontier hosted model + tool harness + UI. The differentiation is engineering, not modeling.

2. Demo-driven hype works because verification is hard. Until someone tries the product at scale, the demo IS the product. Manus restricted access; the demos circulated; the hype peaked before users could falsify it.

3. The Chinese AI narrative is being weaponized. Post-DeepSeek, any Chinese AI launch gets amplified by the “AI race” framing. Sometimes the underlying work is genuinely novel (DeepSeek R1, QwQ-32B). Sometimes it’s standard orchestration with a Chinese label. The narrative often runs ahead of the substance.

Creator POV vs Reddit dissent

Sam Witteveen’s March 17 video on OpenAI Agents SDK — released a week after the Manus reveal — implicitly addresses the cycle: the right response to “Manus is just an agent harness” is to build your own agent harness. OpenAI’s Agents SDK (released the same week) made this trivially easy. By end of March, the “build a Manus clone with OpenAI Agents SDK + Claude” tutorial was a common content piece.

bycloud’s parallel coverage on Meta’s reasoning model and DeepSeek Open Source Week puts the Manus cycle in context: substantive Chinese AI work IS happening (DeepSeek’s actual open-source releases, Qwen’s QwQ), but the viral cycle around Manus was hype-driven, not technology-driven.

The Reddit dissent matured productively:

• “This is just a demo company.” Top critique on r/LocalLLaMA. Valid — Manus was effectively a product-marketing wrapper.
• “But the orchestration is real engineering.” Counter. Also valid — orchestrating 29 tools well is non-trivial.
• “The Chinese AI narrative is being abused for hype.” Macro critique. Also valid — Manus benefited from the post-DeepSeek halo regardless of merit.
• “We need to be more skeptical of demos.” Operational lesson. The community internalized this — by April, the default response to “viral AI agent launch” was skepticism until reverse-engineering happened.

What this means for working engineers in March 2025

Three practical positions:

1. If you want Manus-like capability, build it yourself. OpenAI Agents SDK, Anthropic’s tool-use API, LangGraph, AutoGen — multiple frameworks make a 29-tool agent harness a weekend project. Manus is not magic; it’s product packaging.

2. Discount viral AI demos until reverse-engineered. The Manus cycle is the canonical example. Trust the architecture analysis, not the demo video.

3. Take orchestration engineering seriously. “It’s just a harness” is technically true and substantively wrong. Building reliable agent orchestration at scale is real work. Manus’s actual contribution to the field is showing that the orchestration layer is where consumer-facing AI value lives in 2025.

The honest critique

What this cycle didn’t prove:

• It didn’t prove Chinese AI is overhyped. DeepSeek, Qwen, Kimi all shipped substantive work in 2024-2025. Manus was one company; the broader Chinese AI ecosystem is real.
• It didn’t prove agent harnesses are easy. Reproducing Manus’s demo quality requires real engineering — robust tool design, error handling, prompt engineering, UI work.
• It didn’t prove agents don’t work. Agent harnesses do work for many tasks. The skepticism should be calibrated to specific claims, not categorical.

For most working engineers reading this in mid-March 2025: the Manus cycle is a useful calibration moment. When the next viral AI agent launches, the priors should be: assume hosted-frontier-model + tool harness, wait for reverse-engineering, evaluate the orchestration quality on your actual workload. The hype cycle is now part of the AI product market; engineers who learn to navigate it have an edge.