The launcher button, app icons and taskbar entries were custom elements with click handlers only: none could be focused, named or activated from the keyboard, and the launcher overlay neither took nor returned focus. They are now buttons with accessible names and a visible focus ring. The launcher is a modal dialog that a Super tap or the Apps button opens with focus on its first app; Tab moves between apps, Enter opens one and Escape or another Super tap closes it, returning focus to the Apps button. Each taskbar entry has an activate and a close button reachable with Tab, and focus moves to a remaining control when an entry closes or goes away. Notifications, including the offer to force quit, are announced as status. Servo does not tell the document when its window loses keyboard focus, so weft-servo-shell calls window.weftShellBlurred() then and the launcher closes; the next Super tap opens it again. Servo does not evaluate prefers-reduced-motion either, so the page has no transitions. tests/frame/check_system_ui.py drives the real page on the nested desktop with keys: opening apps from the launcher, reaching the shell with a Super tap from an application, a Super chord that stays with the app and leaves no Super modifier held there, activating and closing apps from the taskbar, the launcher closing when the shell loses focus, and toggling it. It fails without the compositor's Super handling or the focus-loss call.
21 KiB
WEFT OS Architecture
Overview
WEFT OS is a Wayland compositor and application runtime where every app is a WebAssembly component served via a Servo-rendered WebView. The system has no ambient authority: capabilities are declared in wapp.toml, verified at install time, and enforced at runtime.
Components
weft-compositor
Smithay-based Wayland compositor. Implements the zweft-shell-unstable-v1 protocol extension, which allows shell clients (servo-shell, app-shell) to register their surfaces as typed shell slots. Each application session's Wayland connection is handed to the compositor by weft-appd, which binds the client to that session (see security.md). The compositor owns stacking and focus: the system shell's panel is sized to the output and starts beneath application windows, and clicking it brings it to the front as the shell's home, with its launcher, until an application is activated or opens its first window; layout changes keep the stacking order, and a window that maps without taking focus goes beneath the window in front; a session's first window, a clicked window and an activated one are raised, marked activated and given keyboard focus, and when the focused window closes the topmost remaining application window gets focus. Alt+F4 is the compositor's: it asks the focused application window to close (never the panel), and the app shell then exits and its session ends. The Super keys are the compositor's too and never reach an application: a Super tap, pressed and released without another key or a pointer button, brings the panel (the first registered) to the front with keyboard focus and then delivers the tap to it, so the shell's launcher is reachable from any application; keys pressed while Super is held reach the focused window with the Super modifier, but Super's own key events do not. A session's later windows are shown without taking focus. The panel reserves a strip along an output edge for the taskbar with set_exclusive_zone (weft-servo-shell reserves 48 logical pixels at the bottom), and the compositor lays every application window out to fill the remaining work area. weft-appd's ACTIVATE_APP request, which the taskbar sends, asks the compositor to activate a running session's window. Supports DRM/KMS and winit (software/dev) backends.
weft-servo-shell
System UI host. Renders one WebView pointing at system-ui.html using the embedded Servo engine (feature-gated behind servo-embed). Connects to the compositor as window type panel. Dispatches the zweft_shell_manager_v1 event queue each frame. Forwards navigation gestures received from the compositor to weft-appd over WebSocket. Reads the appd WebSocket port and system token from $XDG_RUNTIME_DIR/weft/ and hands both to the page through window.weftAppdEndpoint(port, token); the shell hands the token only to the system UI document and denies top-level navigation away from it, and the launcher shows package names as text, never markup. The system UI works from the keyboard: a Super tap opens or closes the launcher, which lists installed apps by name and keeps focus while open (Tab moves between apps, Enter opens one, Escape closes it and returns focus to the Apps button, with the shell's home still in front); every taskbar entry and its close button is a button reachable with Tab, and Enter on an entry brings its app back. The shell tells the page through window.weftShellBlurred() when it loses keyboard focus, which Servo does not report to the document, and the launcher closes. The page has no transitions or animations, since Servo does not evaluate prefers-reduced-motion.
weft-app-shell
Per-application Servo host. Spawned by weft-appd after the Wasm runtime signals READY. Takes <app_id>, <session_id> and --ui <path>, the UI document weft-appd resolved from the package; it never looks for the package itself. Injects the weftIpc WebSocket bridge into the page. The bridge authenticates with the per-session token from WEFT_BRIDGE_TOKEN and can only exchange messages with its own session. It is installed only in top-level documents inside the application's UI directory, and top-level navigation outside that directory is denied; framed documents never receive the bridge. Every resource the page loads (subresources, fetch(), XHR, workers and WebSocket handshakes) is checked by the shell: the page may load files inside its UI directory, also after symbolic links are resolved, inline data: and blob: resources, about:blank and the session bridge; any other local file or network destination, and every redirect, fails with a network error. Loads Servo does not attribute to the webview, such as navigator.sendBeacon(), are all refused. Network access belongs to the Wasm component, under its fetch grants. Servo's privileged navigator.servo interface, which can change engine preferences, is not exposed to about:blank or about:srcdoc documents (a fork patch; see crates/weft-servo-shell/SERVO_PIN.md). Registers with the compositor as window type application, over the one Wayland connection weft-appd created for its session and passed as standard input (WAYLAND_SOCKET=0). Exits when the appd session ends.
weft-appd
Session supervisor. Listens on a Unix socket (MessagePack protocol) and a WebSocket port (JSON). Before a session exists, appd resolves the package once (see Package resolution) and derives its grants from that package's manifest; the runtime and the app shell receive the resolved component and UI document and do not search the stores themselves. For each session: spawns weft-runtime and waits for its READY, spawns weft-app-shell (WEFT_APP_SHELL_BIN is required) and waits for its READY, and only then reports the session running (APP_READY). A child reports readiness by printing READY <token> on stdout, where the token is a random per-session value appd passes in WEFT_READY_TOKEN; Wasm guests and pages share those stdout streams but cannot read the token, so their output cannot fake readiness. Each wait times out after 30 seconds. TERMINATE_APP on a running session closes it as a user close would: appd asks the compositor to close the session's windows and gives the app shell 5 seconds to exit by itself, for example after saving, before terminating it. The session stays running while the application answers (appd replies with that state), and enters stopping only once it is ending. An application that declares the ask close policy may decline the close (see Closing an application); its window is brought to the front and the session keeps running. A repeated request while the application answers changes nothing, and a session being asked to close is still restored at the next start if appd stops meanwhile. TERMINATE_APP with "force": true terminates the session without asking; the taskbar offers it, as Force quit, for an app still running once it has had time to answer. The stop reason records what happened: a close on request with a clean exit, a failure while closing, the timeout, or a forced stop; stopped is broadcast once the session has settled. A session still starting is stopped at once, also when the request races its readiness, and when appd itself shuts down its sessions are terminated without a close. appd keeps the final state of at most 32 stopped sessions, forgetting those launched earliest. If either child fails to start, fails to become ready or exits, or the session is terminated, the whole session is stopped: both children, the IPC relay (its task, socket and registered sender), the file portal, the compositor association and any image mount are released. The IPC relay is created with the session in $XDG_RUNTIME_DIR/weft (a session cannot start without it); its socket is accessible only to the user and accepts a single connection, which the session's runtime makes before it starts the component. If that connection closes while the session runs, the session is stopped. IPC_FORWARD on the Unix socket never waits: it reports an error when the session has no relay or its queue is full. appd applies cgroup resource limits to the runtime via systemd-run when available.
weft-runtime
WASI Preview 2 + Component Model execution host (Wasmtime 30). Runs the component weft-appd passes with --module <path>, the package's [runtime].module. Provides host imports for weft:app/notify, weft:app/ipc, weft:app/fetch, weft:app/notifications, and weft:app/clipboard. Preopens filesystem paths according to capabilities declared in wapp.toml.
weft-pack
Package management CLI. Subcommands: check (validate wapp.toml + wasm module), sign (Ed25519 signature), verify (verify signature), generate-key, install, uninstall, list, build-image (EROFS dm-verity), info.
weft-file-portal
Per-session file proxy. Runs as a separate process with a path allowlist derived from the session's directory grants; read-only grants (--allow-read) refuse writes. Paths are checked lexically, so .. is blocked but symbolic links are followed. Accepts JSON-lines requests over a Unix socket. Components cannot currently reach that socket, because the runtime grants them no socket access.
weft-mount-helper
Setuid helper binary. Calls veritysetup and mounts EROFS images for dm-verity-protected packages. Its device-mapper device is named after the mountpoint, which weft-appd names with a random token in $XDG_RUNTIME_DIR/weft/mnt. The helper does not yet restrict its callers or the images and mountpoints they pass, so it is not part of a supported installation.
Process Topology
systemd
├── weft-compositor (user)
├── weft-servo-shell (user, after compositor)
└── weft-appd (user, after compositor + servo-shell)
└── per-session:
├── weft-runtime <app_id> <session_id> --ipc-socket <path> --module <path> [--preopen HOST::GUEST::ro|rw]... [--grant CAP]...
├── weft-app-shell <app_id> <session_id> --ui <path>
└── weft-file-portal <socket> [--allow ...] [--allow-read ...]
IPC
| Channel | Protocol | Purpose |
|---|---|---|
| weft-appd Unix socket | MessagePack | appd ↔ other system daemons |
| weft-appd WebSocket (:7410) | JSON | system-ui.html and servo-shell ↔ appd (system role: gestures, app lifecycle); app pages ↔ their session (app role) |
| per-session IPC socket | newline-delimited JSON | weft-runtime ↔ weft-app-shell (weft:app/ipc) |
| weft-file-portal socket | JSON-lines | weft-runtime ↔ file proxy |
WebSocket roles
Every WebSocket connection must complete the upgrade and send HELLO as its first message within 5 seconds, or appd closes it; a first message that is not a valid HELLO is answered with an error (code 401) before the connection is closed. Messages are limited to 1 MiB.
{"type":"HELLO","role":"system","token":"<hex>"}— the token is the content of$XDG_RUNTIME_DIR/weft/appd.systoken(mode 0600), regenerated each time appd starts. A system client may launch, terminate and query sessions. It receives lifecycle broadcasts but never application messages, and cannot inject them (IPC_FORWARDis refused with code 403).{"type":"HELLO","role":"app","session_id":<n>,"token":"<hex>"}— the token is the session's bridge token, passed toweft-app-shellinWEFT_BRIDGE_TOKENand distinct from its readiness token. An app client may only send{"type":"APP_MESSAGE","payload":"<string>"}(at most 64 KiB, no newlines); the payload goes to its own session's Wasm component. It receives only its own session's replies, asAPP_MESSAGE, and is disconnected when the session stops.
Capability Enforcement
Capabilities are declared in wapp.toml under [package] capabilities. One vocabulary (weft_ipc_types::capability) is used by weft-pack check, which rejects unknown strings, by weft-appd, which derives the session's effective grants, and by weft-runtime, which enforces them.
weft-appd derives grants once, before a session exists. LAUNCH_APP is answered with an error and nothing starts when the app ID is malformed (code 400), the package is not installed (404), a declared capability is unknown, unsupported on this host or cannot be satisfied (403), app data exists in both the current and the earlier location (409), or the host cannot provide the resources (500, for example without HOME). All capabilities are checked before the app's data directory is created. Without WEFT_RUNTIME_BIN, appd starts no processes and derives no grants. The runtime does not read the manifest; it receives the grants as arguments:
--preopen HOST::GUEST::ro|rwfor each directory, with the access mode the capability names;--grant <capability>for each host-import capability.
Each capability-controlled host import (fetch, notifications, clipboard) checks its grant on every call and returns an error naming the missing capability when it is not granted. notify and ipc need no capability.
| Capability | Effect |
|---|---|
fs:read:app-data / fs:rw:app-data |
Preopen the app's data directory (see App data) as /data, read-only or read-write |
fs:read:xdg-documents / fs:rw:xdg-documents |
Preopen the documents directory from the XDG user-dirs configuration (XDG_DOCUMENTS_DIR) as /xdg/documents; the launch fails when none is configured |
net:fetch:<host> |
weft:app/fetch to that exact host (a lowercase DNS name or dotted IPv4 address) over HTTP or HTTPS, on any port |
net:fetch:* |
weft:app/fetch to any host |
sys:notifications |
weft:app/notifications |
sys:clipboard:read / sys:clipboard:write |
weft:app/clipboard#read / #write |
hw:gpu:compute / hw:gpu:render |
Not supported; the launch fails |
Fetch does not follow redirects: a redirect is returned to the component as a response, so every destination it requests is checked against its grants. HTTP error statuses are responses too; only policy and transport failures are errors. Only the methods GET, HEAD, POST, PUT, PATCH, DELETE and OPTIONS are accepted, and a component cannot set Host, Content-Length, Transfer-Encoding or other hop-by-hop headers. Connecting times out after 10 seconds and the whole request after 30 seconds, not counting DNS resolution; response bodies are limited to 16 MiB. Fetch requires a runtime built with the net-fetch feature.
Fetch grants name hosts, not addresses: ports are not restricted, and a host that resolves to a loopback or private address (or net:fetch:*) can reach local services. IPv6 literals cannot be granted.
tests/runtime/check_grants.py runs the real runtime on a probe component (tests/components/grants-probe) under each kind of grant.
Package Format
<app_id>/
wapp.toml — manifest (id, name, version, capabilities, runtime.module, ui.entry)
app.wasm — WASI Component Model binary
ui/
index.html — entry point served by weft-app-shell
signature.sig — Ed25519 signature over SHA-256 of (wapp.toml + app.wasm)
Package store roots (in priority order):
$WEFT_APP_STORE(if set)~/.local/share/weft/apps//usr/share/weft/apps/
Package resolution
weft-appd resolves a launch once. A verified image in any store root takes precedence over a directory install in any root, so a user's directory cannot shadow a system image; otherwise the first root with a directory install is used:
- Verified image:
<root>/<id>.app.imgwith its dm-verity hash tree<id>.app.hashand root hash<id>.app.roothash, the namesweft-pack build-imageandbuild-verityproduce. When any of the three exists, the image must mount throughweft-mount-helper; a missing companion, a malformed root hash, a missing helper or a failed mount refuses the launch, and appd never falls back to a directory install. The root hash is read from the store next to the image and is not yet authenticated, so dm-verity detects corruption but not a store whose image, hash tree and root hash were replaced together. The mount belongs to the session and is released when the session stops. - Directory install:
<root>/<id>/wapp.toml.
The package root must be a directory and its manifest a regular file, neither a symbolic link, and the manifest must declare the requested ID. [runtime].module and [ui].entry must be relative paths of plain components, without symbolic links, naming regular files inside that root. The component, the UI document and the capabilities all come from that one manifest. A refused launch reports 400 (invalid ID), 404 (not installed), 403 (invalid package, image or image metadata) or 500 (the host cannot read the package or mount the image).
A directory install can still be changed by its owner while a session runs, and nothing verifies its content at launch.
Closing an application
A user closes an application from the taskbar, which sends TERMINATE_APP, or with Alt+F4 in the compositor; both ask the application's window to close. What happens next is the application's declared unsaved-change policy, [ui].close in wapp.toml:
immediate(the default): the app shell exits at once.ask: the app shell dispatches a cancelableweftcloseevent on the page's top-level window and waits up to 2 seconds for it to be handled. If no listener callspreventDefault(), or the page does not answer in time, the app shell exits. Otherwise the close is declined: the app shell reports this to weft-appd with its readiness token on standard output, so page output cannot forge it, and the session keeps running. The page then lets the user decide, and closes itself withwindow.close(), which Servo allows while the top-level document has a single history entry. A clean exit after a close request, including one the page makes after declining, is recorded as a close on request. A report still unread when a new request arrives can answer that request early; the app shell still closes a page that does not answer.
Notes uses ask: with unsaved changes it offers "Save and close", which closes only after the save is acknowledged and stays open with the error shown when the save fails, "Close without saving", and Cancel.
The close timeout of weft-appd still applies to a close that is not declined: an app shell that neither exits nor declines within 5 seconds is terminated, and the stop reason says so. An application can decline every close, so a forced stop never asks it: it is the user's way to end an application that will not close. A forced stop, the timeout, a crash and appd's own shutdown are never reported as a close on request, and say nothing about whether the application saved.
App data
Each app's private data lives in $XDG_DATA_HOME/weft/app-data/<id> (~/.local/share/weft/app-data/<id> by default), apart from installed packages. Installing, updating or uninstalling a package never removes it. weft-appd creates the directory when a session with an app-data capability starts and makes it accessible only to the user (mode 0700); a symbolic link in its place is refused rather than followed. weft-appd and weft-pack must run with the same HOME and XDG_DATA_HOME to agree on this location; the systemd unit allows weft-appd to write under ~/.local/share/weft.
Earlier versions kept app data inside the user package store, in ~/.local/share/weft/apps/<id>/data, for apps declaring an app-data capability. That directory is moved to the new location in a single rename, which never replaces an existing directory:
- by
weft-appd, on the first launch with an app-data capability; - by
weft-pack uninstallandweft-pack install, before they touch a package directory in the user store (however its path is spelled).uninstallmoves it when the package declares an app-data capability or its manifest cannot be read, and otherwise stops without removing anything; adatadirectory is never deleted with a package.
A package directory left empty by the move is removed. Nothing is moved, and weft-pack stops or the launch is refused, when the new location already exists, even empty (error 409), when the old one is not a plain directory, or when the two are on different filesystems (error 500); the message names both locations so the user can keep one copy and remove the other. The system UI shows such refusals. Packages cannot contain a top-level data entry, so package content is never taken for app data. tests/frame/check_app_data.py checks that existing Notes data arrives byte for byte, that the Notes session then reads and saves it, and that a conflict is refused.
Environment Variables
| Variable | Default | Description |
|---|---|---|
WEFT_RUNTIME_BIN |
— | Path to weft-runtime binary |
WEFT_APP_SHELL_BIN |
— | Path to weft-app-shell binary; required to launch apps |
WEFT_READY_TOKEN |
set by appd | Per-session readiness token passed to weft-runtime and weft-app-shell |
WEFT_BRIDGE_TOKEN |
set by appd | Per-session token weft-app-shell uses to join its session on the appd WebSocket |
WEFT_FILE_PORTAL_BIN |
— | Path to weft-file-portal binary |
WEFT_MOUNT_HELPER |
— | Path to weft-mount-helper binary |
WEFT_APP_STORE |
— | Override package store root |
WEFT_APPD_SOCKET |
— | Unix socket path for weft-appd |
WEFT_APPD_WS_PORT |
7410 |
WebSocket port for weft-appd |
WEFT_EGL_RENDERING |
— | Set to 1 to use EGL rendering in Servo shell |
WEFT_DISABLE_CGROUP |
— | Set to disable systemd-run cgroup wrapping |
WEFT_FILE_PORTAL_SOCKET |
— | Path forwarded to app runtime for file portal |
XDG_RUNTIME_DIR |
— | Standard XDG runtime dir (sockets written here) |