CodexWUI is the static browser frontend of Codex(W)UI. It connects directly to an AISuite codex-bridge WebSocket endpoint with the codex subprotocol. It contains no web server, bridge router, controller authority, or persistent Codex state. Its build and browser qualification require Node.js 22 or newer and Chrome or Chromium. Set CHROME_BIN to its executable if it is outside the usual system paths.

Follow the browser build guide for the AISuite checkout layout, SDK build, application build and release qualification. Run its commands from the repository root.

npm run profile from this directory repeats the large-thread presentation measurement. There is no standalone Node development or production server.

For the shortest launch path, use First run: browser edition.

npm run build:app creates the relocatable static artifact in app-dist/. The standalone packaging project verifies and installs it with:

cmake -S . -B package-build -DCMAKE_INSTALL_PREFIX=/desired/prefix
cmake --build package-build --target codexui-web-artifact
cmake --install package-build --component CodexWebUI

The combined CodexUI build includes this project by default and installs the artifact in share/codexui/web; native-only builds must explicitly configure -DCODEXUI_INSTALL_WEB=OFF. The existing codex-bridge HTTP/WebSocket listener serves /, /index.html, and the generated /assets/ files from that directory while /codex remains the WebSocket upgrade route. A page delivered over HTTPS automatically derives the corresponding same-origin wss://.../codex URL.

The configured bridge URL is retained in browser local storage. Controller/observer roles are not authentication; keep the listener on loopback or behind an external authenticated TLS boundary. Observers may receive broadcasts and read permitted workspace files. Provider-side workspace paths and generated-image paths are displayed as remote metadata; the application does not imply access to the browser machine's filesystem. Failed WebSocket openings release their transport through the SDK detach callback; an explicit retry waits for that release before constructing its replacement.

The bridge, not this static frontend, owns the encrypted listener. A build with AISuite frontend TLS/WebSocket components exposes codex-bridge-wss-ipv4. For a private VPN or another network boundary that admits only authorized users, provide your own certificate chain/key and bind only that network's interface. The following is a deployment template, not a configured public endpoint:

VPN_IP=YOUR_PRIVATE_INTERFACE_ADDRESS
codex-bridge codex --bridge-web-root /path/to/installed/share/codexui/web \
  codex-bridge-wss-ipv4 --disabled=false \
    local --host "$VPN_IP" --port 8443 \
    tls --cert /path/to/server-chain.pem --cert-key /path/to/server-key.pem

Open https://YOUR_CERTIFICATE_DNS_NAME:8443/ from an authorized peer. Its default same-origin connection is wss://YOUR_CERTIFICATE_DNS_NAME:8443/codex; the bridge and browser negotiate the codex subprotocol. The DNS name must resolve to the bound interface and match a certificate trusted by that browser. Restrict private-key permissions and check codex-bridge codex-bridge-wss-ipv4 --help=expanded against the installed build before launch. Other non-Unix frontend instances remain disabled unless explicitly enabled.

Verify page/assets delivery, the WSS handshake, controller/observer behavior and a real prompt. Test that an unauthorized network peer cannot reach the listener. TLS supplies encryption/server identity, not application authentication: do not expose this recipe to the public Internet merely because WSS works. A public deployment needs an independently authenticated boundary that protects both the static application and WebSocket upgrade and preserves /codex and the subprotocol. That boundary's credentials and authorization policy are operator-owned, not built into CodexUI.

• npm test builds TypeScript and runs all presentation, projection, lifecycle, viewport, supporting-surface, and server-render qualification tests.
• npm run build:app verifies the production Vite bundle.
• npm run qualify:browser serves that bundle only for the duration of a headless-Chromium responsive, focus, drawer, and target-size qualification.
• npm run verify:artifact proves that the output is non-empty and relocatable below an arbitrary static base path.
• The web qualification job checks the SDK from AISuite's default branch independently, runs the web suite, records the performance profile, installs the artifact through CMake, and uploads the verified staged tree as codexui-web.

The authoritative scope and exceptions are in ../docs/web/contract-1.0.md.