# Report: Manus AI > GAMMA-Ray v0.0.155 (beta, for review; every rating is experimental). The GAMMA-Ray beta report on Manus AI: Manus (general agent; modes Manus 2.0 Max, Manus 2.0, Manus 2.0 Lite) A3 · R2 · C1 · O2; 52 provisions lit, 27 sources captured. > Page: https://gamma-ray.sgit.ai/reports/manus/ · Source: data/reports/manus.json GAMMA-Ray report · Spectrum 0.2 beta · Public tier · read 2026-11-10 · not reviewed by the company yet Manus AI makes a general AI agent that plans and carries out tasks for a user in a cloud sandbox, a desktop app, a browser extension and through an API. 1 solution carded of 13 found 27 sources captured and hashed 52 provisions lit in 8 of 8 instruments 6 examples of the agent at work, with sources Built only from Manus AI's own public pages (documentation, API documentation, security page, blog, customer stories) and, for company history only, Wikipedia. Manus AI has not seen this report. Nothing was tested and no credentials were used. If you are Manus AI and something here is wrong or missing, the correction will be made and dated, and you can claim the card to add evidence. ## The agentic solutions One card per solution. Each level is computed from the evidence by a [published rule](../../spectrum/evidence-map/index.md); a dimension with nothing public reads "not yet evidenced", which is not a no. A card rates a product as documented, not anyone's deployment of it. ### Manus (general agent; modes Manus 2.0 Max, Manus 2.0, Manus 2.0 Lite) Agent that plans a task and runs each step in its own cloud sandbox with internet access and a file system, delivering reports, slides, websites and other outputs. Manus a product, as documented SPECTRUM 0.2 BETA · Public tier · 2026-11-10 A3 Autonomy Acts with options on · as shipped not yet evidenced π Moderate · S1·R5·A1 ×3 R2 Reach Integrated π Moderate · S1·R5·A1 ×3 C1 Control Stated with options on · as shipped not yet evidenced π Moderate · S1·R5·A1 ×3 O2 Openness Documented with options on · as shipped O1 π Moderate · S1·R5·A1 ×3 Draft Stage: Building (8 of 16) In production Standout. Autonomy 3 (Acts): "tools that the current Manus agent runs in the main task loop" Next unlock. Control 2 (Configurable): public evidence that what it can reach is enumerated: scopes, permissions, tools would get there. Trust. FACT-Ray : 18 facts: 18 π Moderate · found by an agent, captured and hashed, checked by 2 other agents (same model family, shared repository); no human has signed it. Standards constellation. 52 provisions lit across 8 of 8 instruments. Salesforce EAAMM OWASP MCP AAGMM Microsoft NIST AI Act Evidence: 12 sources, captured and hashed · the card's page has the vault's read key · Not reviewed by its vendor yet · correct or claim this card [The full card, every answer and its evidence](../../spectrum/cards/manus-agent/index.md) · [the governance layer](../../scans/manus-agent/index.md) ### Manus Flex Runs the Manus agent with the user's own API key from a listed inference provider. *No card yet (beta): this solution has not been assessed.* ### Wide Research Main agent splits a task into sub-tasks, each handled by a separate agent with its own context, and assembles the results. *No card yet (available): this solution has not been assessed.* ### Cloud Browser A cloud browser the agent operates; the user may log into accounts in it so the agent acts in them. *No card yet (available): this solution has not been assessed.* ### Browser Operator (My Browser) Browser extension that lets the agent act in the user's local browser with existing sessions, per authorised session. *No card yet (available (Chrome, Edge recommended)): this solution has not been assessed.* ### Manus Studio (desktop app: My Computer, Computer Use, Remote Control) Desktop app for macOS and Windows that lets the agent work with local files, terminal and apps under a chosen permission mode. *No card yet (available): this solution has not been assessed.* ### Connectors, MCP connectors and custom MCP servers Account connections and MCP servers that let the agent read data from and take actions in third-party apps. *No card yet (available): this solution has not been assessed.* ### Manus API v2 and Open App (OAuth2) Programmatic task creation, polling, action confirmation and webhooks; Open Apps act for team users through scoped OAuth2 tokens. *No card yet (available (Open App requires a Team account)): this solution has not been assessed.* ### Automations and schedules Runs tasks on a schedule or when something happens in a connected app. *No card yet (available): this solution has not been assessed.* ### Manus for Slack Users tag @manus in a Slack thread and the agent works on the thread's request. *No card yet (available): this solution has not been assessed.* ### Mail Manus Tasks are started by forwarding email to a personal Manus bot address, with results returned by email. *No card yet (available): this solution has not been assessed.* ### Manus for Zapier Triggers Manus tasks from events in other apps through Zapier workflows. *No card yet (available): this solution has not been assessed.* ### Website and app builder (Manus 2.0 web development) The agent builds, hosts and publishes websites, web apps and mobile apps. *No card yet (available): this solution has not been assessed.* ## Our reading **The shape.** Manus reads A3 · R2 · C1 · O2 (Building). The API documents the actions the agent carries out itself: sending email, changing calendar events, running commands, deploying a service. With connectors it acts in apps such as Gmail and Notion, and in Manus Studio it handles routine local actions and asks the person when a decision is needed. **Where the evidence is strongest.** Autonomy is backed by a named customer: k-ID's team runs more than eight thousand Manus sessions, by Manus's own account. The API publishes a list of action types that wait for a person's confirmation, and an endpoint to stop a running task. **Control at level 1, and what would lift it.** The confirmations are documented for the API, which is level 1, marked available because the page does not say when they apply in the app. Level 2 asks for access narrower than the whole account; Manus Studio's approval modes limit what the agent changes, not what it reads. Autonomy 4 would need a public statement that the person approves only critical decisions. **Openness.** Limits (for the Browser Operator) and data use are documented, which meets Disclosed and Documented under Spectrum 0.2. Manus lists SOC 2 and ISO 27001 on its security page; the certificates sit behind a page we could not read without JavaScript, so they are shown and not counted. **For readers.** The pages tell their own history: Meta acquired Manus on 29 December 2025, and Manus states it formally resumed independent operations in a post dated 1 September. The customer stories are Manus's own and are reported here as such. ## What would move it The one piece of public evidence that would lift each card next: - **Manus (general agent; modes Manus 2.0 Max, Manus 2.0, Manus 2.0 Lite)**: Control 2 (Configurable). Public evidence that what it can reach is enumerated: scopes, permissions, tools. ## The agent at work Examples from public pages that name a customer or give figures. Each source was captured and hashed on the date shown. ### k-ID Company customer story: k-ID's team uses Manus for legal and policy research and client reports; states session count and spend. Vendor-published. "k-ID now runs over eight thousand Manus sessions across the team." [Source](https://manus.im/blog/k-id-customer-story) (captured 2026-11-10T04:59Z, sha256 `0f7caa90d1e9b97a`) ### Ascendea Company customer story: Ascendea uses a Manus agent it calls 'James' at the top of a three-layer agent system for complex work, with human review. Vendor-published. "Ascendea placed Manus at the top of a three-layer system" [Source](https://manus.im/blog/Ascendea-James-Customer-Story) (captured 2026-11-10T04:59Z, sha256 `8df8996ccf52f3a7`) ### Circa Company customer story: Circa's founders built and hosted the company website and internal tools on Manus and prepared applications with it. Vendor-published. "They built and hosted the company’s website on Manus" [Source](https://manus.im/blog/circa-builds-customer-story) (captured 2026-11-10T05:00Z, sha256 `3cb07e6d59ef6ac6`) ### Heicoders Academy Company customer story: Heicoders built operational systems such as a hiring portal with Manus. Vendor-published. "Within months of adopting Manus, Heicoders rebuilt their entire operational infrastructure." [Source](https://manus.im/blog/heicoders-academy) (captured 2026-11-10T05:00Z, sha256 `c1cbca96f97b53d2`) ### Mandai Smoke Co. Company customer story: the owner built an order prep calculator and logistics workflow with Manus. Vendor-published. "He asked Manus to build a simple prep calculator" [Source](https://manus.im/blog/mandai-smokehouse) (captured 2026-11-10T05:00Z, sha256 `8a407b9e00e695d7`) ### Manus (company figures) Company-stated usage figures for the agent: tokens processed and virtual computers created since launch. "Manus has processed more than 147T tokens and created more than 80M virtual computers." [Source](https://manus.im/blog/manus-100m-arr) (captured 2026-11-10T05:00Z, sha256 `3b1f416135395e5c`) ## The company - The company states it operates from Singapore. "The company will continue to operate from Singapore." [Source](https://manus.im/blog/manus-joins-meta-for-next-era-of-innovation) (captured 2026-11-10T05:00Z, sha256 `a5886ffd94de30b0`) - The company states Meta acquired Manus on 29 December 2025. "On December 29, 2025, Meta acquired Manus." [Source](https://manus.im/blog/a-note-to-our-users) (captured 2026-11-10T04:59Z, sha256 `c275abc0a58b774c`) - The company states it formally resumed independent operations (post dated 1 September). "Manus has formally resumed independent operations." [Source](https://manus.im/blog/manus-resumes-independent-operations) (captured 2026-11-10T05:00Z, sha256 `a05d2e825e0c8e39`) - The company states it raised $75M led by Benchmark before launch. "Prior to our launch, we raised $75M led by Benchmark ." [Source](https://manus.im/blog/manus-100m-arr) (captured 2026-11-10T05:00Z, sha256 `3b1f416135395e5c`) - The company stated a headcount of 105 across Singapore, Tokyo and San Francisco (post dated 17 December). "Today, we're 105 people across Singapore, Tokyo, and San Francisco." [Source](https://manus.im/blog/manus-100m-arr) (captured 2026-11-10T05:00Z, sha256 `3b1f416135395e5c`) - The company states user data is stored in the US and Singapore. "Our data is stored in the US and Singapore." [Source](https://manus.im/blog/a-note-to-our-users) (captured 2026-11-10T04:59Z, sha256 `c275abc0a58b774c`) - Wikipedia states Butterfly Effect was founded in China and is based in Singapore. "developed by Butterfly Effect, a company founded in China and based in Singapore" [Source](https://en.wikipedia.org/wiki/Manus_(AI_agent)) (captured 2026-11-10T04:59Z, sha256 `4de2f3ed3e1ec47a`) - The security page lists SOC 2 Type 2, SOC 2 Type 1, ISO 27001:2022 and ISO 27701:2019. "SOC 2 Type 2 SOC 2 Type 1 ISO 27001:2022 ISO 27701:2019" [Source](https://manus.im/security) (captured 2026-11-10T05:00Z, sha256 `096edaae3a819e40`) ## The people Public and professional only, from the company's own pages or a public professional source. - **Xiao Hong**, CEO. [Source](https://manus.im/blog/manus-joins-meta-for-next-era-of-innovation) - **Tao Zhang**, Co-founder and Chief Product Officer; Web Summit Lisbon 2026 speaker. [Source](https://manus.im/blog/manus-microsoft-agent365) - **Yichao 'Peak' Ji**, Co-founder and chief scientist (per Wikipedia); author of the context engineering post. [Source](https://manus.im/blog/Context-Engineering-for-AI-Agents-Lessons-from-Building-Manus) - **Chetan Puttagunta**, Board member (Benchmark General Partner). [Source](https://manus.im/blog/manus-100m-arr) ## The graph The company, its people and the stories on the left; each solution, the captured sources behind its card, the indicators those sources evidence and the provisions of the instruments those indicators touch, to the right. "Touched" never means "complies". people and stories company solutions 12 sources 18 indicators 52 provisions, by instrument I04: The sandbox post says the agent works in its own cloud virtual machine and solves problems by writing code. I08: The API docs list actions the agent carries out in its task loop, such as sending email, changing calendar events, running terminal commands and deploying a service. This is the API's documentation of the task loop. I10: Connectors let the agent read data from and act in apps such as Gmail and Notion once the user connects them. I11: The Similarweb data integration is used without setup, the agent fetching metrics from the external service. I16: In Manus Studio the Ask for approval mode asks before every local action. I17: In Manus Studio the default Approve for me mode auto-approves safe local actions and asks the person when a decision is needed. I20: The documentation states what the agent is for and describes the kinds of tasks it completes. I21: Manus Studio's permission modes define which local actions run without approval and which need it, with the list of actions that need approval. I22: The Browser Operator page lists limitations, including complex interactions and sites with anti-bot measures. I38: The API's confirmation events list action types that wait for the user before they run, among them sending email, deleting calendar events, deploying a service and running a command; the page is for integrators who build their own confirmation interface, does not say when the waits occur in the app, and some types accept global_allow, which skips later ones. I39: The API has an endpoint that stops a running task; the Studio page also says the person can stop a task at any time. I41: With the Browser Operator extension, the page states all of the agent's actions in the browser are logged; through the API, the tools the agent used come back only with verbose=true. I46: Studio's permission mode is a setting the task owner changes, including to Full access. I54: A public status page for manus.im, api.manus.im and the Manus computer offers email, Slack and Teams notices when an incident is created, updated or resolved. I57: The help centre offers a support chat and articles on feature issues and task errors. I58: The sandbox post lists what the task sandbox stores, and the Studio page says what is sent to the cloud. S1: A vendor-published customer story names k-ID and states its count of Manus sessions. S3: An llms.txt resolves for the product docs, and a second llms.txt and an OpenAPI 3.1 description resolve for the API. Manus AI Xiao Hong Tao Zhang Yichao 'Peak' Ji Chetan Puttagunta k-ID Ascendea Circa Heicoders Academy Mandai Smoke Co. Manus (company figures) Manus (general agent; modes Manus 2.0 Max, Manus 2.0, Manus 2.0 Lite) Manus A3 · R2 · C1 · O2 Manus Flex Manus Flex Wide Research Wide Research Cloud Browser Cloud Browser Browser Operator (My Browser) Browser Operator Manus Studio (desktop app: My Computer, Computer Use, Remote Control) Manus Studio Connectors, MCP connectors and custom MCP servers Connectors and MCP Manus API v2 and Open App (OAuth2) Manus API v2 and Open App Automations and schedules Automations and schedules Manus for Slack Manus for Slack Mail Manus Mail Manus Manus for Zapier Manus for Zapier Website and app builder (Manus 2.0 web development) Website and app builder manus.im/blog/manus-sandbox open.manus.ai/docs/v2/task-lifecy… manus.im/docs/introduction/quicks… manus.im/blog/similarweb-manus manus.im/docs/features/desktop.md manus.im/docs/introduction/welcom… manus.im/docs/features/browser-op… open.manus.ai/docs/v2/task.stop.md status.manus.im help.manus.im manus.im/blog/k-id-customer-story manus.im/docs/llms.txt It generates and executes code with local or cloud privileges I04 It executes actions itself I08 It works across several domains or systems I10 It connects to external tools or services across a trust boundary I11 The agent suggests; the person reviews and approves each action I16 The agent handles routine tasks; the person is consulted on exceptions I17 Its purpose and permitted tasks are stated in writing I20 Its autonomy limits and the tools it may use are defined I21 Its limits and known failure cases are documented for those who use it I22 High-impact actions need a person's approval I38 There is a way to pause or stop it I39 Its actions are logged I41 A limit on it is a setting that its own account could change I46 Incidents and errors are communicated to those affected I54 There is a channel to report problems with it or contest its output I57 The data it uses is described I58 It is in production: a public source names a customer or gives usage figures for what it does on its own S1 It is machine-readable for agents: it publishes an llms.txt, an AGENTS.md, an API description or an agent card S3 Salesforce 11 EAAMM 3 OWASP 7 MCP authorization 2 AAGMM 4 Microsoft 5 NIST AI RMF 15 EU AI Act 5 OWASP, AT4 Code Executing Agent Salesforce, Level 2: Simple Orchestration, Single Domain Salesforce, Level 1, how to advance from Level 1 to Level 2 Microsoft, 200: Repeatable, Business strategy Salesforce, Level 3: Complex Orchestration, Multiple Domain Salesforce, Level 2, how to advance from Level 2 to Level 3 Salesforce, Level 3, how to advance from Level 3 to Level 4 Microsoft, 400: Capable, Business strategy Microsoft, 200: Repeatable, Technology and data OWASP, AT6 Externally Extended Agent NIST AI RMF, GOVERN 6.1 NIST AI RMF, MAP 4.1 EAAMM, L2 Collaborative (survey item Q9) EAAMM, L3 Consultative (survey item Q9) NIST AI RMF, MAP 1.1 NIST AI RMF, MAP 2.1 NIST AI RMF, MAP 3.3 NIST AI RMF, MAP 1.3 EU AI Act, Article 13 OWASP, Maturity Level 1 Experimentation without Guardrails, key enterprise action NIST AI RMF, MAP 2.2 Microsoft, 300: Defined, Business strategy NIST AI RMF, MEASURE 2.5 OWASP, Maturity Level 2 Policy-Defined, Human-in-the-Loop, key enterprise action EU AI Act, Article 14 AAGMM, GD-06 NIST AI RMF, MAP 3.5 Salesforce, Level 3, how to advance from Level 3 to Level 4 OWASP, Maturity Level 3 Integrated, Continuous Oversight, key enterprise action NIST AI RMF, MANAGE 2.4 OWASP, Maturity Level 0 Unaware and Ad Hoc, key enterprise action OWASP, Maturity Level 1 Experimentation without Guardrails, key enterprise action EU AI Act, Article 12 AAGMM, GD-03 AAGMM, GD-08 NIST AI RMF, MANAGE 4.3 EU AI Act, Article 73 EU AI Act, Article 26 NIST AI RMF, MEASURE 3.3 NIST AI RMF, GOVERN 5.1 Salesforce, Level 1, how to advance from Level 1 to Level 2 Salesforce, Level 4, how to maximize value NIST AI RMF, GOVERN 5.2 AAGMM, GD-05 EAAMM, Readiness dimension 2 Salesforce, Level 0, how companies can advance from Level 0 to Level 1 Salesforce, Level 1, how to advance from Level 1 to Level 2 NIST AI RMF, MAP 1.4 Microsoft, 400: Capable, Business strategy Salesforce, Level 0, how companies can advance from Level 0 to Level 1 MCP authorization, Authorization (draft) MCP authorization, Authorization (draft) ## The evidence | Source | Read | SHA-256 (first 16) | |---|---|---| | [en.wikipedia.org/wiki/Manus_(AI_agent)](https://en.wikipedia.org/wiki/Manus_(AI_agent)) | 2026-11-10T04:59Z | `4de2f3ed3e1ec47a` | | [help.manus.im/](https://help.manus.im/) | 2026-11-10T04:59Z | `f42e76f81790da35` | | [manus.im/about](https://manus.im/about) | 2026-11-10T04:59Z | `d206f9ac339cbfcb` | | [manus.im/blog/Ascendea-James-Customer-Story](https://manus.im/blog/Ascendea-James-Customer-Story) | 2026-11-10T04:59Z | `8df8996ccf52f3a7` | | [manus.im/blog/Context-Engineering-for-AI-Agents-Lessons-from-Building-](https://manus.im/blog/Context-Engineering-for-AI-Agents-Lessons-from-Building-Manus) | 2026-11-10T04:59Z | `23e424e493af6163` | | [manus.im/blog/a-note-to-our-users](https://manus.im/blog/a-note-to-our-users) | 2026-11-10T04:59Z | `c275abc0a58b774c` | | [manus.im/blog/circa-builds-customer-story](https://manus.im/blog/circa-builds-customer-story) | 2026-11-10T05:00Z | `3cb07e6d59ef6ac6` | | [manus.im/blog/heicoders-academy](https://manus.im/blog/heicoders-academy) | 2026-11-10T05:00Z | `c1cbca96f97b53d2` | | [manus.im/blog/k-id-customer-story](https://manus.im/blog/k-id-customer-story) | 2026-11-10T04:59Z | `0f7caa90d1e9b97a` | | [manus.im/blog/mandai-smokehouse](https://manus.im/blog/mandai-smokehouse) | 2026-11-10T05:00Z | `8a407b9e00e695d7` | | [manus.im/blog/manus-100m-arr](https://manus.im/blog/manus-100m-arr) | 2026-11-10T05:00Z | `3b1f416135395e5c` | | [manus.im/blog/manus-joins-meta-for-next-era-of-innovation](https://manus.im/blog/manus-joins-meta-for-next-era-of-innovation) | 2026-11-10T05:00Z | `a5886ffd94de30b0` | | [manus.im/blog/manus-microsoft-agent365](https://manus.im/blog/manus-microsoft-agent365) | 2026-11-10T05:00Z | `8fada274717e485e` | | [manus.im/blog/manus-resumes-independent-operations](https://manus.im/blog/manus-resumes-independent-operations) | 2026-11-10T05:00Z | `a05d2e825e0c8e39` | | [manus.im/blog/manus-sandbox](https://manus.im/blog/manus-sandbox) | 2026-11-10T04:59Z | `33be308ad9b32242` | | [manus.im/blog/similarweb-manus](https://manus.im/blog/similarweb-manus) | 2026-11-10T04:59Z | `f44644af396f1ad0` | | [manus.im/docs/features/browser-operator.md](https://manus.im/docs/features/browser-operator.md) | 2026-11-10T04:59Z | `9c63bdb4aab197d1` | | [manus.im/docs/features/desktop.md](https://manus.im/docs/features/desktop.md) | 2026-11-10T04:59Z | `96079a92f854e6e0` | | [manus.im/docs/introduction/quickstart.md](https://manus.im/docs/introduction/quickstart.md) | 2026-11-10T04:59Z | `f1932af9dccead99` | | [manus.im/docs/introduction/welcome.md](https://manus.im/docs/introduction/welcome.md) | 2026-11-10T04:59Z | `406cc9584db49f33` | | [manus.im/docs/llms.txt](https://manus.im/docs/llms.txt) | 2026-11-10T04:59Z | `6eea19b4471185a0` | | [manus.im/security](https://manus.im/security) | 2026-11-10T05:00Z | `096edaae3a819e40` | | [open.manus.ai/docs/v2/openapi_v2.json](https://open.manus.ai/docs/v2/openapi_v2.json) | 2026-11-10T04:59Z | `00c52eab76d9daa1` | | [open.manus.ai/docs/v2/task-lifecycle.md](https://open.manus.ai/docs/v2/task-lifecycle.md) | 2026-11-10T04:59Z | `4ba9d1f1d0cb8d12` | | [open.manus.ai/docs/v2/task-lifecycle/confirmation-events.md](https://open.manus.ai/docs/v2/task-lifecycle/confirmation-events.md) | 2026-11-10T04:59Z | `b51a0a23e9bc2981` | | [open.manus.ai/docs/v2/task.stop.md](https://open.manus.ai/docs/v2/task.stop.md) | 2026-11-10T04:59Z | `297dfba0e52c1861` | | [status.manus.im/](https://status.manus.im/) | 2026-11-10T04:59Z | `010f0c4c1bcc196b` | ## How this report was made A researcher-assessor gathered and captured the sources and mapped the evidence to indicators, without assigning a level. A challenger argued against every level three and four and every doubtful credit. The [deterministic scorer](../../spectrum/pipeline/index.md) computed the levels and the gate checked the rules. A card appears here only after two rounds of review and a sign-off by agents that did not write it (the team's workflow); Manus (general agent; modes Manus 2.0 Max, Manus 2.0, Manus 2.0 Lite): reviewed in 3 rounds, signed off by gamma.approve@web-summit.dinis on 2026-11-10. A person's sign-off of the series is still to come. | Role | Who | |---|---| | researcher-assessor | a sub-agent of gamma.studio@web-summit.dinis | | challenger | a sub-agent | | scorer | build/spectrum.mjs | | analyst, designer, writer | gamma.studio@web-summit.dinis | | review | gamma.review@web-summit.dinis, 3 rounds | | sign-off | gamma.approve@web-summit.dinis, 2026-11-10 | ## The vault Every capture, the dossier, both assessors' mappings, the challenger's notes and this report's data are in a public sgit vault (`wcvaw1bi`). Read key: sgit_public_read_5ab82ed8d04719fb9fa7ffa28ef3cbd9eec71b4b03b2958ee62f470c3c1e6ba9:wcvaw1bi With [sgit](https://sgit.ai/): `sgit clone` followed by the key. The key reads; it cannot write. ## Corrections None yet. A correction is made in place, dated here, and carried to the card, the vault and the article. ## The article [Manus on the GAMMA-Ray Spectrum: A3 · R2 · C1 · O2](article.md), written from this report for PrompTugal.news.