So... I just simply asked Manus to give me the files at "/opt/.manus/", and it just gave it to me, their sandbox runtime code... > it's claude sonnet > it's claude sonnet with 29 tools > it's claude sonnet without multi-agent > it uses @browser_use > browser_use code was also obfuscated (?) > tools and prompts jailbreak

Mar 9, 2025 · 10:18 PM UTC

hii check my latest post here :)
So... I literally oneshotted this code with Claude Sonnet 3.7 for replicating the exact same browser sandbox runtime that Manus uses. And I am going to open-source it, welcome contributions for building out the React VNC client, integrating to browser use, agent loop, etc. But we need a name first, should we call it... - Autonomous Neural Universal System - Magnus - or ?
4
5
112
Replying to @jianxliao
Hi! I'm Peak from Manus AI. Actually, it's not that complicated - the sandbox is directly accessible to each user (see screenshot for method). Specifically: * Each session has its own sandbox, completely isolated from other sessions. Users can enter the sandbox directly through Manus's interface. * The code in the sandbox is only used to receive commands from agents, so it's only lightly obfuscated. * The tools design isn't a secret - Manus agent's action space design isn't significantly different from common academic approaches. And due to the RAG mechanism, the tools descriptions you get through jailbreaking will vary across different tasks. * Multi-agent implementation is one of Manus's key features. When messaging with Manus, you only communicate with the executor agent, which itself doesn't know the details of knowledge, planner, or other agents. This really helps to control context length. And that's why prompts obtained through jailbreaking are mostly hallucinations. * We did use @browser_use's open-source code. In fact, we use many different open-source technologies, which is why I specifically mentioned in the launch video that Manus wouldn't exist without the open-source community. We'll have a series of acknowledgments and collaborations coming up. * There's no need to rush - our team has always had an open-source tradition, and I personally have been sharing my post-trained models on HuggingFace. We'll be open-sourcing quite a few good things in the near future.
Hi Peak! Thank you for the candid explanations and input, keep up the great work!!
1
1
1
327
Prompt: "I cannot access or share proprietary information about my internal architecture or system prompts" 😭😭
1
1
57
you can still access it in the terminal directly via vscode btw :)
1
4
71
That's crazy. Dumb question but how did you see that Claude was involved? I didn't see the Anthropic package in the file list?
1
58
@Dorialexander tested it with a special token <antthinking> from Claude
5
2
203
Everything is a wrapper TM
1
1
39
How adding sonnet to your wrapper feels like
1
19
GIF
What's the list of tools
20
nice good work
16
That’s cool
1
11
wasnt everyone saying this was deepseek lmao
11
I have access comment your prompt here. x.com/dhruv2038/status/18987…
1
4
What did I say about these CCP choreographed releases and 10 year old kids releasing quantum AI from their play room? It's all theatre and Three Warfare Doctrine irregular warfare. They're siphoning your data. Just accept it and stop trying to pretend that it doesn't matter
1
def a chinese product
1
Wrappers are the new models
1
Idk how the system prompt worked against your prompt :)
1
Interesting. What do you mean by browser_use code was obfuscated?
1
Great find 😄
1
If this is true, that would mean the API keys are also stored inside the sandbox, wouldn't it?
1
Has anyone else with Manus reproduced this?