Latest in AI
Manus Websites Can Now Be Installed as Desktop Apps in Chrome
Manus is making generated websites easier to return to, without requiring a separate native-app build or an app-store release.
Manus says every website made with its builder can now be installed as a desktop app through Chrome. The October 27 announcement adds a simpler way to access a published site outside a normal browser tab. It does not announce native desktop binaries or an app-store publishing service.
How to install a Manus website
The company's official instructions are short: publish the website in Manus, open that published site in Chrome, then click Install in the address bar. Manus says the workflow works with every site made using its builder, without additional setup.
The announcement does not specify a separate installation charge or a plan-by-plan eligibility table. It also does not describe support in other browsers. Chrome is the route Manus documents, so that is the route to evaluate rather than assuming identical behavior everywhere.
A web app is different from a native build
Chrome already supports installing websites as web apps. Google's web-app documentation explains that an installed web app can be reached through the computer's launcher, with its settings managed through Chrome.
For Manus users, the change makes that installation path available for their generated sites. The announcement does not describe converting website code into a separate native application or producing an installer for distribution outside the browser.
This is also different from the Manus Desktop App, which is the company's own agent application. Here, the thing being installed is a website someone built with Manus.
What this changes for small tools
Consider an internal dashboard that a team opens several times a day. A direct application entry can make it easier to find than a link buried in a conversation or one more browser tab. That is a practical distribution improvement even when the underlying software remains a website.
It could be useful for lightweight calculators, client portals and recurring internal workflows. A public landing page that someone visits once gains less from installation. The benefit depends on whether people have a reason to come back.
Installation does not solve the harder product questions. A generated tool still needs sensible permissions, reliable data and a useful workflow. Putting it in an app-like window does not establish that those parts are ready.
What not to assume
Manus has not specified offline guarantees, notification support or native operating-system integrations for this update. Google notes that web-app capabilities vary and some functions still require an internet connection. A site that depends on a remote API or database should not be treated as offline-capable just because it has been installed.
The sensible test is therefore simple: can someone install the published tool, return to it easily and complete the same real task reliably? For AI-built software, reducing the distance between a working prototype and a tool people actually revisit can matter more than adding another generation option.
I’m Paras. I work at the intersection of AI, engineering and distribution.
I help technical founders turn product updates into clear launch stories that developers and founders read and share.