vtx.foundation draft d03

VTX 1 · core · beta draft d03

VTX 1 Wire Specification: core

Oct 11, 2026, revised Nov 16, 202639 pagesALPN vtx1-d03MIT licence

§19Conformance

Three conformance classes set the minimum each implementation supports. Everything above it is negotiated.

Class Must support
Cell client TLS over TCP; channels 0, 1, 2 and 4; grids and their ops; input.keys; the token and tls-cert auth methods; the trusted zone for approvals and permissions
Component client All of the cell client, plus the core catalog, the clipboard channel and webauthn
Server TLS over TCP and WebSocket; the webauthn and token auth methods; fallback rendering (Section 18); the application interface over stdio, unless the server embeds its application. The VT engine is optional

Profiles and extensions. The classes are the floor; the profiles name what a client renders above it. Profile 0 is a plain VT terminal reached through a gateway and needs no VTX client. Profile 1 is a cell client, Profile 2 a component client that also renders vector surfaces, images and themes, and Profile 3 a client that also renders pixel and window surfaces, audio and video, and offers redirection and WebAssembly components. No extension is mandatory: a peer offers each with its capability keys, and peers that share none still talk. ext/registry.json gives each extension the lowest profile whose clients can offer it, and its status: draft (not yet implemented), candidate (implemented, still open to change) or stable (frozen).

Extension Lowest profile Status What it adds
Surfaces 1 2 draft Vector, image and grid surfaces
Themes 1 2 draft Branded themes on the root and regions
Composites 1 2 draft Custom components from declarative catalogs
Media 1 3 draft Audio and video streams, pixel surfaces, keyboard lock
Transfer 1 1 draft Downloads, uploads, folders and files on the clipboard
Exec 1 1 draft Remote commands and port forwarding
Devices 1 1 draft Push wake-ups, device keys and enrolment
Viewers 1 1 draft Shared sessions, roles, recording and calls
Sensors 1 2 draft Device sensors, gamepad datagrams, surface accessibility
Windows 1 3 draft The device's own windows for remote and VTX applications
Displays 1 3 draft Multi-monitor sessions
Brokering 1 1 draft App lists, launching and session routing
Drives 1 3 draft The device's folders in a session
Printers 1 3 draft Printing on the device's printers
Media Devices 1 3 draft The device's microphones, speakers and cameras in a session
Smart Cards 1 3 draft The device's smart card readers in a session
USB 1 3 draft USB devices the user picks, in a session
WASM 1 3 draft WebAssembly components, each drawing its own surface

Two bindings, a host binding and a gateway binding, sit beside the extensions and add nothing to the wire: Wayland Host 1 fixes how a Wayland compositor serves a session, and RDP Bridge 1 how a gateway puts Windows session hosts behind VTX.

Test vectors. examples/vectors.json in the definitions bundle holds known answers: QUIC varints, a CREDIT frame, an APPROVAL with its digest and WebAuthn challenge, an OIDC nonce, an update sent as two UPDATE frames, and an x509 sign-in and card-signed approval made with a published test key. tools/validate.py recomputes or verifies each one; an implementation conforms on these points when it produces the same bytes.