My Computer by Manus AI

Automate files, apps, and workflows with Manus Desktop

Productivity

Artificial Intelligence

Tech

Moving agents from cloud sandboxing to direct local execution feels like a major shift.

Most real workflows live across files, terminals, and apps — so bridging that gap unlocks a lot of practical use cases.

Curious how you handle safety boundaries when executing local commands.

Is there a permission system for different levels of actions, or does every command require manual approval?

Great to see Manus moving in the local workspace. A lot of productivity use-cases still remain locally (local files, tools, and apps). I'd be interested in seeing how it works compared to Claude Cowork.

Excited to use this and test the concurrent tasks within the Manus browser itself. I've recently invested more time into Cursor IDE and also Github Desktop so I'll see how I can combine this with the Manus mobile app and 'work on the go'

This is a really compelling step for desktop automation. Most AI tools today operate in a cloud sandbox, which limits what they can do with local files and apps. Having Manus run directly on your machine feels like a fundamentally different approach compared to cloud-based automation platforms like Zapier or Make. The ability to organize local files, trigger CLI commands, and even build apps without code is impressive. I'm curious about the security model here — since it has deep access to your local system, how do you handle permission scoping and ensure sensitive files or credentials aren't accidentally exposed during automated workflows?

Can Manus run multiple projects at the same time on my computer? Or does it handle one workflow at a time?

Moving from a cloud sandbox to direct local execution is the real unlock here. Most “agents” hit a ceiling because they can’t touch the actual environment where work happens—files, CLI tools, dev setups. This closes that gap in a meaningful way.

The remote triggering + idle compute angle is especially interesting. That starts to look less like a tool and more like a persistent background worker tied to your personal machine.

The hard part, though, is control. Once you give an agent CLI-level access, the UX and safety model become the product.

How are you thinking about permission granularity over time—does Manus evolve toward predefined trust scopes (file ops vs system-level commands), or will users always need to approve actions step-by-step?

This seems compelling but leaves me wondering if Manus still burn through credits without completing tasks fully post-acquisition. If that has improved, this could be worth the download!

This looks really interesting . How does Manus handle permissions for local tasks? Do we have fine grained control over what it can and can’t do on our machine, or is it an all-or-nothing approval for commands?

Bringing AI agent capabilities directly to the local desktop is a game-changer. As someone who values local-first workflows, I’m curious about the performance side—does running Manus locally consume significant CPU while it's processing CLI tasks in the background?

Giving this a shot! Looks a lot like Claude desktop, and I am OK with that, happy to see a familiar Ui

congratulations seems like Manus is further igniting the Computer fire. more is always better.

Moving Manus from cloud-only sandboxing to direct local machine access via CLI execution is the natural next step — most real productivity workflows involve local files, dev environments, and desktop apps that a cloud-only agent simply can't touch, so bridging that gap unlocks an entirely different class of automation tasks. The remote task triggering is a compelling feature for power users, but how does Manus handle permission scoping on local execution — is there a granular approval system for different command types, or does the user approve each terminal command individually?