Skip to content
Start here1 min read

FAQ

Short answers about data, browsers, models, userscript reach and self-hosting.

Updated Nov 6, 20251 min readEdit this page
On this page

Is Lumo open source?#

The extension repositories are public. Lumo does not currently include a license file; Lumo Userscripts is MIT. Read the repository before redistributing a build.

Does Lumo send my pages to a server?#

There is no Lumo relay. Model requests go from your browser to the provider you configure. If you choose a local model, page content does not leave the machine.

Which browsers are supported?#

  • Lumo: Chrome and Chromium-based browsers with MV3. A Firefox build is available from source.
  • Lumo Userscripts: Chrome 138+ with Allow User Scripts enabled.

Can the agent create userscripts?#

Yes, when you enable the endpoint in Lumo Userscripts and approve the caller. The agent gets list, get and diagnostics immediately; creating, editing, enabling, installing and trashing scripts needs a second Allow writes switch, and every write is audited.

Can I use a local model?#

Yes. Configure an OpenAI-compatible endpoint such as Ollama or a local gateway. Vision and tool calling depend on the model you choose.

Do userscripts run on chrome:// pages?#

No. Chrome does not allow extensions to inject into privileged pages, the Web Store, or other extensions. The manager shows a permission empty state instead of pretending the script ran.

How do updates work?#

Lumo Userscripts checks script updates and asks before installing a version that needs more permissions. Lumo itself updates through the Chrome Web Store or by replacing an unpacked build.

Can I self-host this website?#

Yes. It is a static Vite build. Run npm run build and serve build/client from any static host. Without the Worker that rewrites origins, set VITE_SITE_URL so canonical and social URLs point at your domain.

Still stuck?

Open an issue on the relevant repository. Include the browser version, the product version and the exact status or log line.