Skip to main content

Module capability

Module capability 

Source
Expand description

The one place each host capability is decided. lx.supports(), the FFI capability bitmask, and the optional lx.* members all read these, so they cannot drift apart.

Modules§

build
What the binary carries, independent of what an app declared. The native SDKs’ capability bitmask reports this.

Functions§

app_use
Driving this product’s own windows and its command line. computerUse already contains it, so it answers for both — the same rule the local control surface enforces.
browser
Managed browser tabs and the browser shell.
browser_use
Driving the in-app browser’s tabs. capabilities.browser is the prerequisite — there is nothing to drive without the engine — so both have to be on. The declared flag alone would let lx.supports lie.
computer_use
Driving the whole machine: screenshots, synthetic input, the a11y tree.
media_capture
Realtime capture tracks declared by the host.
notifications
Host notifications.
proxy
The in-app browser’s HTTP proxy. capabilities.proxy declares it and capabilities.browser is its prerequisite — a proxy with nothing to proxy is not a capability — so both have to be on.