Features

The app groups several local tasks into one workflow. The exact controls can vary with the installed release and platform; the important distinction is what each control changes.

Profile and engine controls

Choose a browser-family profile, start or stop the local STATIC engine, and inspect its status. The profile coordinates supported values across HTTP, TLS, JavaScript, and, on a configured Linux path, packet handling. It is a target for supported signals, not a guarantee that all signals match. See Profile anatomy and JavaScript runtime.

Certificate trust and routing

STATIC creates a local CA so the browser can accept leaf certificates issued for intercepted HTTPS connections. The app handles the host trust prompt; routing controls direct browser or system proxy traffic to STATIC’s local listener. These are separate steps. What 404 changes explains their scope and removal.

Windows distribution and updates

On Windows, the managed path provisions the 404 WSL2 distribution, stages its runtime configuration, and starts STATIC there. The app also manages distribution updates as described in the existing desktop guide. See Rose provisioning for the signed manifest and archive relationship and Platform notes for the host boundary.

Account and cleanup

Some desktop builds use account or license activation; follow the prompts presented by your installed build. The app’s cleanup and reset flow is the first place to stop routing and remove managed trust and runtime state. Review the host changes before manually deleting data or unregistering a WSL distro. The self-hosted CLI does not use the managed app workflow.