Starling — the first real desktop written by AI

">

GitHub

Early preview · v0.2 · Ubuntu<br>The first real desktop<br>written by AI

Others have pointed AI at a desktop before. They ran in a browser tab, or<br>stopped at a mock-up. Starling drives the GPU directly and runs<br>Chrome, Slack and Zoom. It was written by AI, directed by one<br>person, over six months.

Install Starling<br>See what's real about it

335K

Lines of first-party Swift, C and C++

6 months

First commit to a desktop you can log into

Person directing the work

~2,000

Commits, and still moving

Line count excludes vendored dependencies. Most of it — about 273K — is the<br>Flutter→Swift framework port that the whole system rests on; the desktop<br>itself, its Wayland and X11 servers and the bundled apps come to roughly<br>62K. Both repositories are public —<br>desktop and<br>engine — so<br>every number here is yours to check.

What "real" means

Not a browser tab.<br>Not a mock-up.

"AI built a desktop" has been claimed before, and it has usually meant one<br>of three things: a desktop metaphor drawn inside a web page; a convincing<br>screenshot of something that was never logged into; or a from-scratch<br>system that does boot, but only ever runs the handful of programs written<br>for it.

One test separates them: does it run software it didn't<br>write? That is a desktop's actual job — to host programs made by<br>strangers, years apart, in toolkits it doesn't control, and keep them all<br>on one screen without any of them knowing about each other. A system that<br>only runs its own apps has skipped the hard part.

Starling is the session. It talks to DRM/KMS and owns the<br>display. It reads the raw input devices. It is a Wayland compositor, and it<br>hosts an X server for the apps that still need one. You pick it at the login<br>screen, sign in, and it's your desktop until you log out — running Chrome,<br>Slack and Zoom, none of which have ever heard of it.

The usual AI desktop

Runs inside a browser tab

Windows are s that can't hold a real program

Or it boots — but runs only the apps written for it

Screenshots of a design that was never logged into

Starling

Drives the GPU through DRM/KMS, as the session

Runs software it didn't write — Chrome, Slack, Zoom

Speaks Wayland and X11 natively, at once

Every screenshot here is a running session

The screenshot below is the test that settles it. Zoom is an X11 client;<br>Chrome is a Wayland one. Two programs written by strangers, composited into<br>one scene, on one GPU path, by a desktop that didn't exist six months ago.

Zoom on X11 and Chrome on Wayland — one desktop, one GPU path, no session picker.

Why it matters

The cost of building a desktop just collapsed

For three decades, building a Linux desktop has been the work of<br>institutions. GNOME and KDE are extraordinary pieces of engineering,<br>sustained by hundreds of contributors across decades. That isn't a<br>criticism of them — it's a measure of what a desktop has cost to build.

And that cost is why there are so few. Why the ones we have are hard to<br>change from outside. Why a genuinely new idea about how a desktop should<br>work has had almost nowhere to go except a fork, an extension, or a patch<br>queue someone else controls.

One person, six months, a complete desktop. Not by cutting scope — it<br>drives the GPU, runs Chrome and Zoom, survives a monitor being unplugged.

That number is the whole argument. If a single person can now reach this<br>point, then the constraint on Linux desktop development was never<br>imagination and never taste. It was labour. And labour is exactly what<br>just got cheap.

The interesting consequence isn't Starling. It's the ten<br>desktops after it — attempted by people who never had a decade to give, who<br>would have looked at the size of the job and picked a smaller one. That<br>floor has moved, and the rate at which Linux desktops get built should move<br>with it.

This is the time to build.

The desktop

And it's a complete one

Not a proof of concept with the interesting parts missing. Every<br>screenshot below is the real thing, captured from a running session.

Tiling and floating, both first-class

Floating windows by default. Flip one switch and everything arranges<br>itself master-and-stack, the way a tiling window manager does —<br>whatever you are working in holds the master pane, everything else<br>stacked beside it.

Flip it back and every window returns to exactly where it was floating.<br>No extension, no separate desktop to switch to, nothing to relearn.

Settings → Appearance → Tiling Windows

Tiling on — the master pane on the left, everything else stacked beside it.

Spaces and Mission Control

Slide between virtual desktops, carry a window along as you go, or pull<br>back with one key and see every space at once. Anything you send<br>fullscreen quietly becomes a space of its own.

Drag a window between spaces from the overview, or add a new one from<br>the strip along the top.

Ctrl + ↑ for the overview · Ctrl + ← → to switch

Mission Control — spaces along the top, windows spread below.

Monitors...