Architecture

Lasso separates the browser experience from source-code access. The browser overlay handles selection and interaction; a local bridge handles filesystem-aware operations.

The request path

Browser overlay → local WebSocket bridge → source context
Browser overlay → API / realtime service → hosted features

The bridge runs on loopback and receives only the context needed for the current action. Proposed edits return as a reviewable diff.

Local Host

Lasso Host provides stable .lasso domains and proxies project traffic. HTTP uses 6766; HTTPS uses 6767. WebSocket and HMR traffic are forwarded to the project runtime.

Security boundaries

• Credentials live in the local Lasso directory.
• Filesystem changes require an explicit apply action.
• The host listens on loopback by default.
• HTTPS local domains enable browser capabilities such as microphone access.

Next steps

Start with the quickstart or browse the CLI reference.