AutoUI desktop paths
Shared view definitions support Vue and native desktop environments, with separate coverage for execution, code generation and platform integration. The AutoOS product repository organizes desktop surfaces; the language framework supplies execution, rendering and system integration.
Current progress described as of 2026-10-01
Browser and native preview
AutoUI has working desktop paths. auto run uses the Vue/browser path; auto run -r vm executes Auto UI sources in the VM with an iced native interface. These paths share UI definitions, while renderers provide their own platform facilities.
Native development supports hot reload. The path and the kind of change determine which running state can be preserved. Shared definitions aim for consistent layout, interaction, and themes; they do not promise identical text rasterization across platforms.
Compiled applications and composition
Code generation and a2r provide compiled paths. Desktop shell, application rendering sources, and the composition host are connected through window and rendering contracts. RenderQueue and RQHost work belong to this boundary; they do not imply that every existing VM application has migrated to native execution.
auto-os assembles the desktop and applications, while auto-lang implements the language and framework. The current launch manifest primarily declares VM applications. Host integration and platform coverage must be checked for each path and feature.
From application UI to AutoOS
A virtual desktop adds shared window management, workspaces, a launcher, and notifications around application UI. It reuses the existing host system. Early Linux composition-host work exists, with independent systems remaining a longer-term direction.
View the actual desktop · Read the OS overview · Desktop architecture · Compiled shell design · AutoUI overview