Starling 0.5 shipped on September 20, and it has an optional 3D desktop mode that renders your session as a walkable waterfront city.

Starling is the Linux desktop built around its own Wayland compositor, written in Swift, and produced in large part with AI assistance. The project states that Claude Fable 5.1 worked on this release.

What the mode actually is

From the release announcement:

“Starling keeps the familiar 2D desktop and adds a walkable 3D waterfront city. Open the control panel and choose 3D Desktop to change perspectives. The city includes moving boats, traffic and clouds, a clock tower, sunset lighting, and cream, bronze and sage window chrome.”

The detail that makes it more than a screensaver is that the windows stay real:

“Chrome, Video Player, Files, Terminal and the other desktop apps remain real windows. Switch between them with Alt + Tab, or bring a live preview forward from the rail. Double-click a window’s outer title bar to center the view on it. Popups follow their parent window in the scene.”

Popups following their parent window into a 3D scene is the sort of thing that sounds trivial and is not. Wayland positions child surfaces relative to parents in two dimensions, and keeping a context menu attached to a window that now has a position and an orientation in a rendered world is real compositor work rather than a visual effect.

The multi-monitor handling is similarly non-trivial:

“Each display has its own scene and camera. Walking, turning or pointer-driven parallax on one display leaves the other display’s view unchanged. Scene rendering shares a backend while keeping each output’s camera and render target independent.”

Independent cameras per output with a shared rendering backend is the correct architecture, and it is more thought than most novelty features get.

We have been here before

Sun Microsystems built Project Looking Glass around 2004: a 3D desktop where windows could be rotated and had backs you could write notes on. It was demonstrated widely, admired briefly, and used by essentially nobody.

The reason was never rendering. It was that 3D adds a dimension you have to navigate, and navigation is cost. A 2D desktop lets you reach any window in one motion. Walking to a window is slower than clicking one, every time, and no amount of atmosphere changes that arithmetic for someone working.

Starling’s version is explicitly optional and sits alongside the normal 2D desktop, which is the right framing. It is a mode you enter, not a paradigm you adopt.

The part worth watching

The interesting thing about Starling is not the city. It is that a functioning Wayland compositor with multi-output scene management exists at version 0.5, written in a language with almost no Linux desktop presence, largely through AI-assisted development.

That sits in the same month as the rest of this ecosystem’s AI argument: LLMs catching error-path bugs across the 7.3 kernel cycle, AI-located bottlenecks producing a 70% incremental build speedup, Debian’s vote on responsible use, and the origination rule that cost Void Linux 113 packages.

Compositors are not a forgiving target. They deal with buffer lifetimes, input routing, output timing and protocol correctness, and getting them subtly wrong produces flicker, dropped input and crashes rather than clean failures. How well this one holds up under real use is the question that matters, and it will take longer than a release announcement to answer.

Trying it

0.5 also adds Windows support through WSL2 on Ubuntu 26.04 using the RDP display mode, which is a practical way to look at it without committing a machine.

For the more conventional new desktops in this space, our coverage of COSMIC and Omarchy 4.0 covers projects aiming at daily use rather than at demonstrating what a compositor can be talked into doing.