01 Manus AI Claims to Be the World's First General AI Agent — MIT Technology Review Went to Find Out
When Manus AI launched in early 2025, it spread across the internet with a velocity usually reserved for consumer apps, not enterprise AI tools. MIT Technology Review was among the first credible outlets to get hands-on access, and their assessment was both impressed and skeptical in specific, measurable ways.
"Since the general AI agent Manus was launched last week, it has spread online like wildfire. And not just in China, where it was developed by the Wuhan-based startup Butterfly Effect." — MIT Technology Review
Manus is not a chatbot. It does not sit in a text box waiting for you to ask questions. You give it a high-level goal — "build me a portfolio website," "create a competitive analysis of the CRM market," "make a playable browser game" — and it figures out all the intermediate steps on its own. It breaks the goal into sub-tasks, assigns them to different internal agents, and executes them autonomously. The underlying models are a combination of Anthropic's Claude 3.5 Sonnet and fine-tuned versions of Alibaba's Qwen, orchestrated through a multi-agent architecture.
The buzz attracted serious attention. Twitter cofounder Jack Dorsey and Hugging Face product lead Victor Mustar were among the influencers who praised its capabilities. The Discord channel surpassed 186,000 members. But MIT Technology Review noted the elephant in the room:
"Very few people have had a chance to use it. Currently, under 1% of the users on the wait list have received an invite code." — MIT Technology Review
This creates a classic hype asymmetry: the people talking about Manus are mostly people who have watched demos, not people who have used it extensively. The people who have used it extensively have a more complicated story to tell — one involving credit depletion, unfinished tasks, and output that requires significant human cleanup.
The technology itself is real. Manus scored competitively on the GAIA benchmark (General AI Assistants), which measures an agent's ability to complete real-world tasks autonomously. It uses a multi-agent architecture that is architecturally sophisticated — not a single model pretending to be autonomous, but multiple specialized agents coordinating through an orchestration layer. The problem is not the technology. The problem is the economics, the polish, and the gap between demo conditions and daily use.
02 What Manus Can Actually Build — Real Output Examples and Their Limitations
The headline capability is real: Manus can build functional things from single prompts. One user documented it creating a playable "Google CEO Simulator" game in approximately one hour from a single prompt. Another had it build a functional Linktree-style personal homepage in under 30 minutes. It can code simple browser games, generate working web pages, create images, compile research reports, and build presentations.
A user on Medium documented their firsthand experience:
"Created a playable 'Google CEO Simulator' game in about 1 hour from a single prompt. Built functional Linktree-style personal homepages in under 30 minutes." — Luluyan, Medium
These outputs are impressive for a zero-code, zero-configuration starting point. You describe what you want in plain language, and 30-60 minutes later, you have a working thing. For prototyping, for proof-of-concept demos, for "I need something to show in tomorrow's meeting," this is genuinely useful.
But the quality gap between "functional" and "production-ready" is where Manus consistently falls short:
"The quality is a mixed bag. The output often lacks polish. A generated webpage might have a wild color scheme, or the code might have small bugs that a developer has to fix anyway." — NinjaTech AI comparison
The tasks Manus handles well share common characteristics: they are self-contained, they have clear success criteria, they do not require deep domain knowledge, and the output format is well-defined. Simple games, portfolio sites, market analysis reports, data compilation tasks — these are Manus's sweet spot.
The tasks it handles poorly: anything requiring polish, stability under edge cases, integration with existing systems, or domain-specific accuracy. The generated code has bugs. The designs are generic. The research reports are broad rather than deep. For a professional deliverable, you will spend time fixing what Manus produces — sometimes more time than it would have taken to build from scratch.
"As a beta product, it's reportedly prone to crashing and server overloads. It's a closed-off system. You can't easily hook it up to your existing business software." — NinjaTech AI comparison
The closed system limitation is significant. Manus operates in its own sandbox. It cannot access your company's internal databases, APIs, design systems, or knowledge bases. Every output is generated from general knowledge, which means it cannot learn your brand voice, your code conventions, or your business context. For companies with established systems, this makes Manus useful for greenfield prototypes but not for extending existing products.
One user documented the experience of trying to use Manus for a real business deliverable on Medium:
"Manus can code simple games, generate working web pages, create images, and do deep research. But the output often needs significant cleanup before it's client-ready." — Luluyan, Medium
The pattern across user reports is consistent: Manus excels at generating a first draft of something new and struggles with refining, integrating, or maintaining something existing. This is a fundamental characteristic of multi-agent architectures — they can spin up fresh work quickly, but they lack the deep context needed to work within constraints. A human developer understands your design system, your naming conventions, your deployment pipeline. Manus starts from zero every time.
The stability issues compound the quality concern. Users report server overloads during peak usage, tasks that stall mid-execution, and occasional complete failures where the agent starts a task and produces nothing. For a product charging $39-$199/month, operational reliability should be a given — and by most accounts, it is not yet at that level.
03 The Credit System — How $199/Month Can Disappear in a Single Afternoon
Manus's pricing looks reasonable at first glance. It is not. The credit system is where the economics break down for many users, and the frustration in the community is palpable.
The pricing tiers as of late 2025:
Free: $0/month. 1,000 starter credits plus 300 daily credits. 1 concurrent task. This sounds generous until you learn what credits actually buy.
Basic: $19/month. 1,900 credits (plus 1,900 promo credits during limited-time offer). 2 concurrent tasks.
Plus (Starter): $39/month. 3,900 credits (plus 3,900 promo). 3 concurrent tasks.
Pro: $199/month. 19,900 credits (plus 19,900 promo). 10 concurrent tasks.
Team (Beta): $39/member/month. 3,900 credits per member.
The problem is not the price per tier — it is the credit consumption rate. Every action the agent performs consumes credits. Writing one line of code, creating one slide, making one API call, running one search query. A moderately complex task does not consume 10 or 20 credits. It can consume hundreds.
"Users have reported that a single, moderately complex task can blow through over 900 credits. Some even used up their 1,000 free starter credits on their very first request." — eesel.ai pricing analysis
Read that again: 900 credits for one task. The free tier gives you 1,000 starter credits. A single request — not a complex one, a moderately complex one — can consume 90% of your free allocation. Users who signed up expecting to evaluate the product with several test tasks found themselves locked out after their first attempt.
Three specific design decisions make the credit system particularly frustrating:
No cost estimation before execution: Manus does not tell you how many credits a task will cost before you start. You describe what you want, hit enter, and discover the cost only after credits are deducted. For a $199/month product, this is an extraordinary lack of transparency.
No credit rollover: Unused credits expire at the end of the month. If you pay for 19,900 credits on Pro and only use 5,000, the remaining 14,900 vanish. There is no banking unused credits for heavy-usage months.
Tasks stop mid-execution: If credits run out during a task, the work stops. You get unfinished output with no refund for the credits already consumed. Imagine a research report that cuts off at page 3 of 10, or a website build that generated the frontend but never connected the backend. The partial work is often useless.
The Reddit community at r/ManusOfficial has multiple threads documenting credit depletion frustrations. Users report entering what they thought were simple tasks and watching their credit balance plummet in real time with no way to pause or cancel.
To put the credit economics in concrete terms: on the Free tier (1,000 starter credits + 300 daily), a user might get 1-2 moderately complex tasks before credits are exhausted. On the Basic tier ($19/month, 1,900 credits), you might get 2-4 tasks. On Plus ($39/month, 3,900 credits), maybe 4-8 tasks. On Pro ($199/month, 19,900 credits), roughly 20-40 tasks per month — if tasks average 500-1,000 credits each. But the variance is enormous. A simple "make me a portfolio page" might use 200 credits. A "research this market and build me a presentation" might use 2,000. The unpredictability is the core frustration.
The promo credits (matching the monthly allocation as a limited-time offer) double the initial value but create a misleading first impression. Users sign up, get double credits, have a good experience, and then hit the wall in month two when promo credits expire and their effective budget halves. This is a common SaaS onboarding pattern, but it is particularly painful when credit depletion means unfinished work with no recovery path.
The comparison to ChatGPT Plus is stark. ChatGPT Plus costs $20/month for effectively unlimited GPT-4o usage plus rate-limited access to o3, o4-mini, Deep Research, and all other features. Manus costs $39-$199/month for credit-limited access where a single complex task can consume your monthly allocation.
"When you put this next to something like ChatGPT Plus, which is about $20 a month for pretty much unlimited use, the value proposition looks shaky." — Future AGI analysis
04 Under the Hood — Multi-Agent Architecture and Why It Both Impresses and Fails
Understanding why Manus produces impressive demos but inconsistent real-world results requires understanding its architecture. Manus is not a single AI model — it is a multi-agent system where multiple AI models operate independently on different aspects of a task.
The orchestration layer receives your high-level goal and decomposes it into sub-tasks. Different agents handle different sub-tasks: one agent might research the topic, another designs the visual layout, another writes the code, another compiles the final output. The agents run in a sandboxed environment that provides them with tools — web browsers, code executors, file systems — to complete their work.
The models powering these agents are Anthropic's Claude 3.5 Sonnet for complex reasoning tasks and fine-tuned versions of Alibaba's Qwen for efficiency-sensitive operations. This multi-model approach is not unique to Manus — it is a common pattern in agentic AI systems — but the specific combination and the orchestration quality determine real-world performance.
The GAIA benchmark (General AI Assistants) was the primary public benchmark for evaluating Manus's agent capabilities, and it scored competitively against other agent systems. But benchmarks and production use diverge in predictable ways: benchmarks use well-defined tasks with clear success criteria, while real-world tasks are ambiguous, have implicit requirements, and need to integrate with existing context.
The multi-agent architecture explains both the strengths and weaknesses. When sub-tasks are cleanly separable — research a topic, then write a report about it, then format it as a webpage — the division of labor works well. Each agent handles what it is good at. But when sub-tasks have dependencies — the design must match the content, the code must implement the design, the database schema must support the features — coordination failures emerge. The code agent does not know what the design agent decided. The research agent does not know what the code agent can implement.
This is why output "often lacks polish." The individual components are competent. The integration between components is where quality degrades. A generated webpage might have well-structured HTML but a "wild color scheme" because the design agent and the code agent did not share aesthetic context. The code might function but have "small bugs" because the testing agent did not anticipate edge cases the code agent introduced.
Competing approaches like OpenAI's Codex agent, Claude Code, and Cursor's background agents take a fundamentally different architecture: they use a single powerful model with tools, rather than multiple specialized models coordinating. The single-model approach sacrifices parallelism for coherence — one model understands the entire context, so integration quality is inherently higher, but execution is sequential rather than parallel.
05 Manus vs ChatGPT vs Devin vs Claude — The Honest Comparison Nobody Wants to Make
The competitive landscape for autonomous AI agents is crowded, and each product makes different tradeoffs. The comparison that matters is not feature lists — it is what happens when you give each tool a real task and evaluate the output.
Manus vs ChatGPT Plus ($20/month): ChatGPT Plus offers far more predictable costs. For $20/month you get unlimited GPT-4o, rate-limited o3 and o4-mini, Deep Research, Canvas, Projects, Memory, voice mode, and image generation. The feature breadth is incomparably wider. What ChatGPT lacks is autonomous execution — it does not build things end-to-end without your involvement. You have to guide each step. Manus's value proposition is autonomy: give it a goal and walk away. But autonomy at $39-$199/month with unpredictable credit consumption versus guided interaction at $20/month with predictable unlimited use is a value comparison Manus consistently loses on paper.
Manus vs Devin: Devin, from Cognition Labs, targets software engineering specifically. It sets up development environments, writes code, runs tests, and debugs. For coding tasks, Devin's focused specialization typically produces better results than Manus's generalist approach. Manus is broader — it can research, design, code, and present — but shallower in each vertical.
Manus vs Claude with Computer Use: Anthropic's Claude can now use a computer — clicking buttons, filling forms, navigating websites. This gives it similar autonomous execution capabilities to Manus but backed by a single, more coherent model (Claude Opus or Sonnet). The tradeoff: Claude's computer use is slower and more expensive per task, but the output quality tends to be more consistent because there is no multi-agent coordination to break down.
Manus vs Cursor/Codex Agents: For the specific use case of coding, both Cursor's background agents (70-80% one-shot success rate at $20/month) and OpenAI's Codex (SWE-bench scores of ~80%) outperform Manus on code quality and reliability. These tools are purpose-built for software development with deep IDE integration, repository understanding, and test-driven workflows. Manus can write code, but it is not a coding tool — it is a general agent that happens to have coding as one capability.
The honest assessment: Manus's unique value is end-to-end autonomous execution across multiple domains (research + design + code + presentation) from a single prompt. No other tool does this as seamlessly. But the credit system, the quality inconsistency, the closed ecosystem, and the lack of cost predictability undermine that value proposition for sustained professional use. It is impressive for demos. It is frustrating for daily work.
06 Where Manus Actually Makes Sense — The Tasks Worth Spending Credits On
Despite the limitations, there are specific use cases where Manus's autonomous execution model delivers genuine value — where the alternative is either hiring a freelancer, spending hours doing it yourself, or not doing it at all.
Rapid prototyping for non-technical founders: If you have an app idea and no coding ability, Manus can produce a working prototype — a clickable website, a simple game, a data dashboard — that you can show to potential investors, cofounders, or early users. The prototype will not be production-quality, but it demonstrates the concept. The alternative — hiring a developer for a weekend prototype — costs $500-2,000. Manus can do a rough version for the cost of one Pro month.
Competitive research reports: Ask Manus to research competitors in your market and produce a structured report with pricing, features, positioning, and market share data. The agent searches the web, compiles information, and generates a formatted document. The output needs fact-checking — AI agents hallucinate data points — but as a first-draft research document that you verify and refine, it saves hours of manual research.
One-off web pages for events or campaigns: Landing pages, event registration sites, portfolio pages. These are self-contained, have clear requirements, and do not need to integrate with existing systems. Manus can produce them end-to-end, and the quality is acceptable for short-lived pages where "good enough" is the standard.
Data compilation and presentation: When you need information gathered from multiple web sources and compiled into a presentation or report, the multi-agent architecture actually works well. The research agents gather data while the formatting agents structure it. The output is a polished-looking document that saves significant manual compilation time.
The tasks to avoid giving Manus: anything requiring production-grade code quality, anything that needs to integrate with your existing tech stack, anything requiring domain-specific accuracy (medical, legal, financial content), and anything where partial completion (due to credit depletion) would be worse than not starting at all.
A practical credit management strategy: start every Manus task with a clearly scoped, minimal version. Instead of "build me a full CRM application," start with "build me a single-page contact list with add and delete functionality." Evaluate the output and credit consumption. If the quality is acceptable and the credit cost is reasonable, incrementally expand the scope. This prevents the 900-credit surprise on an ambitious first request.
Another strategy from users who have found sustainable ways to use Manus: front-load research and planning outside Manus, then use Manus only for execution. Instead of asking Manus to "research the CRM market and build me a competitive analysis presentation," do the research yourself with ChatGPT's Deep Research (which is cheaper and higher quality for research tasks), then give Manus a detailed specification: "Build a 10-slide presentation using this data [paste data]. Slide 1: title slide. Slide 2: market overview with these 4 data points. Slide 3: competitive matrix comparing these 5 companies." The more specific your input, the fewer actions the agent takes, and the fewer credits it consumes. Manus excels at execution when the plan is clear — it is the exploration and research phases that consume credits disproportionately because the agent searches, reads, evaluates, and often backtracks.
The concurrent task limits matter for users trying to maximize throughput. On the Free tier, you get 1 concurrent task — you cannot start a second task until the first finishes. Basic gets 2, Plus gets 3, and Pro gets 10. For power users who batch tasks (morning: queue 5 research reports; afternoon: queue 3 web page builds), the concurrent task limit determines how quickly your credit allocation converts into completed work. The Pro tier's 10 concurrent tasks paired with 19,900 credits enables a workflow where you start 10 tasks simultaneously and review outputs within hours — but only if credit consumption per task stays reasonable.
07 The Alternative Stack — What to Use Instead of Manus for Each Use Case
For most professionals, the best approach is not using Manus for everything but assembling the right tool for each task category. Here is the practical alternative stack:
For research and analysis: ChatGPT Plus Deep Research ($20/month) outperforms Manus's research capabilities while costing less and providing unlimited usage. Deep Research scored 26.60% on Humanity's Last Exam versus 20.32% for the best individual model. It browses the web, reads multiple sources, and produces cited reports — the same thing Manus does, but with better quality and predictable pricing.
For code generation: Cursor Pro ($20/month) with background agents or GitHub Copilot Pro ($10/month) with the coding agent. Both produce higher-quality code than Manus, integrate with your existing development environment, and support iterative development workflows. Cursor's 70-80% one-shot success rate on coding tasks versus Manus's inconsistent output quality is not a close comparison.
For web page and app building: Lovable.dev (from $25/month) is purpose-built for full-stack web application generation. It includes Supabase integration for databases, Stripe for payments, and one-click deployment. The credit system is more transparent, and the output quality for web applications is consistently higher than Manus because it is specialized for this exact task. Bolt.new and Vercel's v0 are also viable for different scopes — v0 for components, Bolt for quick prototypes, Lovable for full MVPs.
For design and visual assets: Lovart AI or Figma with AI features. Manus can generate visuals, but dedicated design tools produce higher-quality, more consistent results with better editing capabilities.
For the specific "give it a goal and walk away" workflow: This is Manus's genuine differentiator. If you specifically need autonomous end-to-end execution across research, design, and code from a single prompt with no intermediate guidance, Manus is the only tool that delivers this at consumer-level pricing. The question is whether that specific workflow is worth the credit uncertainty and quality inconsistency. For many users, the answer is: occasionally, for the right task.
For users who want to experiment with AI agent capabilities across multiple platforms — ChatGPT Plus for research, Cursor for coding, various tools for specialized tasks — services like acccup.com provide access to accounts across these platforms without the friction of managing multiple subscriptions and verifications during an evaluation period. When you are comparing five different AI tools to find the right stack, the account provisioning overhead is a real barrier that aggregated access solves.
08 The Honest Verdict — When to Use Manus, When to Skip It, and What Comes Next
Manus AI is a genuinely ambitious product. The multi-agent architecture that decomposes goals into parallel sub-tasks, executed autonomously across research, design, and code, is the future of how AI tools will work. The problem is that Manus is the future arriving too early — with credit economics that punish exploration, output quality that requires human cleanup, and a closed ecosystem that prevents integration with existing workflows.
Use Manus when: You need a rapid prototype or proof-of-concept for something self-contained. You are a non-technical person who needs a working demo and the alternative is hiring a freelancer. You need competitive research compiled into a presentable format and have credits to spare. You want to experience what autonomous AI agents feel like before the technology matures.
Skip Manus when: You need production-quality output. You need to integrate with existing systems. You are cost-sensitive — the credit system makes budgeting impossible. You need the same task done reliably multiple times — the output quality varies between runs. You have access to ChatGPT Plus, which covers the research use case better, and Cursor or Copilot, which cover the coding use case better, both at lower cost with more predictable pricing.
The fundamental tension in Manus's business model is that the tasks where autonomous execution is most valuable — complex, multi-step, cross-domain work — are exactly the tasks that consume the most credits and produce the most inconsistent output. The tasks where output quality is highest — simple, well-defined, single-domain work — are the tasks you could accomplish more cheaply and predictably with existing tools.
What comes next is predictable: the major AI labs are all building similar autonomous agent capabilities. OpenAI's Agent Mode in ChatGPT, Anthropic's computer use capabilities in Claude, Google's agent features in Gemini — these are converging toward the same goal Manus is pursuing. When GPT-5 or Claude Opus 5 can autonomously execute multi-step goals with the quality and reliability of their current chat interfaces, and the pricing is bundled into a $20-40/month subscription, the credit-based standalone agent model becomes untenable.
Manus's window is now. It is the first to market with a consumer-accessible general AI agent. The experience is worth having, with eyes open about the costs and limitations. Use the free tier's 1,000 starter credits wisely — try one well-defined, moderately scoped task and evaluate whether the output quality and the credit economics justify upgrading. For many users, the answer will be: impressive technology, not yet worth paying for monthly. And that is an honest answer for a product that is genuinely ahead of its time but not yet ready for the daily workflow.