Your browser.
Your desktop.

First boot

1. Open over HTTPS Load the desktop from a secure origin and keep the tab open while the offline installer saves the full local payload.
2. Watch the progress count Progress counts completed, verified files — not network bytes. If a download fails, retry; already verified files are reused.
3. Create your local account Complete the local account setup, then sign in to reach the desktop.

The download logo

The installer uses the same four-pane blue SVG as the favicon, with subtle motion that respects reduced-motion settings. It is embedded locally, not downloaded from a logo service.

What works offline?

The bundled desktop, local files, fonts, wallpapers, BitBot resources and bundled app code are cached. Online browsing, remote Store apps, live maps/weather/news, music services and checking for releases require a connection. No static site can automatically archive every external website it can open.

Where are my files and password?

The profile and virtual file system live in browser storage. Login uses local password verification, not Firebase or a cloud account. It is not a substitute for device security. Export important files before clearing site data or switching browser profiles.

How do updates work?

Each boot schedules one automatic check after successful login, using the raw GitHub main-branch update feed. A failed check shows an error rather than silently falling back to old metadata. Restarting or reloading checks again; locking and unlocking does not. You can pause them or use Check for updates manually. Install now saves and verifies the new local payload before switching builds and restarting. A failed download preserves the installed build. The next boot confirms installation in history. About and Settings display the running build, not merely the server's advertised version.

Troubleshooting

• Download incomplete: reconnect and retry. Close extra WebOS tabs if activation stalls.
• Storage unavailable: use a normal HTTPS browser tab, allow site storage or use online-only mode.
• Feed newer than files: deployment may be incomplete. Wait and retry; do not clear all your browser data.
• App needs internet: reconnect for its remote service. The desktop can still operate offline.
• Old release after deployment: check Windows Update. Installing once replaces the old worker; an ordinary reload intentionally keeps your installed offline build.

Build from source

git clone https://github.com/bittuhere/win11webos.git
cd win11webos
npm ci
npm run build

Deploy the contents of build/ to Cloudflare Pages (build command npm run build, output build). Use npm run preview for the header-aware, clean-URL local preview and npm run verify for the build checks. The build emits a full hashed offline manifest and service worker. Development mode intentionally skips offline installation.

Maintainers should read the deployment guide, documentation index and docs/DISCOVERABILITY.md in the repository.