Core developers
Windows adapter status
Windows is a compilation target for the shared Go contracts. Native Host execution and workload isolation on Windows remain unsupported. A Windows client must preserve unavailable and unknown capability states.
Compilation reaches the shared contract layer. A request requiring a native execution boundary stops at admission.
Read the support diagram
The shared protocol codecs can be compiled independently of native execution. The currently unsupported Windows process, journal and listener paths fail closed. There is no qualified Windows service or workload boundary to select for a required isolated run.
Native integration work
A Windows Host would need an authenticated local transport, service lifecycle, credential storage, owned-process control and workload-scoped enforcement evidence. Job Objects and named pipes are proposed platform mechanisms. Their names describe possible implementation choices, not measured protection.
Compile checks cover compatibility of the selected sources. Qualifying a native Windows backend would also require live OS, hardware where applicable, installation and recovery checks for its specific workload. Native module contracts · Verified Apple silicon workload · Verified Linux workload