Status

Where the project is, in plain terms. This page is rewritten as things land.

What works today

• The compositor is feature-complete against its spec and has been the author's only desktop for months on a three-monitor NVIDIA hybrid laptop. Five tiling algorithms, the workspace model, window rules, native screenshots, XWayland via xwayland-satellite, and in-place recovery from a GPU reset with client windows surviving.
• The shell bar is complete: per-monitor bars with workspaces, systray, audio and microphone mixer, network, bandwidth, MPD, weather, BTC, feeds, clock and timezones.
• Screen sharing works through atrium-portal (PipeWire, hybrid GPU included).
• The base system runs without elogind, polkit, NetworkManager, or systemd: seatd, doas, pam_rundir, wpa_supplicant, dhcpcd, udevil, PipeWire.

The line to an installable desktop

1. Next Finish atrium-network. Live status that is always true, wireguard visibility, VPN sessions that can stop what they started.
2. Queued Shell modules. Power menu, launcher, on-screen display, lock screen.
3. Queued Settings panel v1. A curated set of knobs edited through the compositor's IPC, format-preserving, so hand-edited config survives.
4. Queued Packages. xbps templates for every component, a signed binary repository, and an atrium-desktop meta-package that replaces the build-from-source path.
5. Queued Curated app list and family defaults.
6. Queued An ISO. void-mklive with the atrium repository and a config overlay: live boot, install, first login lands in atrium.
7. Queued Floating window mode. A floating-default mode for people who are not ready for tiling.

Steps 1 to 3 finish the desktop. Steps 4 to 6 make it installable. Packaging starts early and absorbs components as they land.

Until then

Atrium can be built from source on an existing Void Linux install. The getting started pages cover the build, the session setup, and the system pieces the compositor expects.