YSERVER 1.5 adds Reverse PRIME to its Rust X11 server

A developer has been writing a full X11 display server from scratch in Rust, and it just reached version 1.5. YSERVER 1.5 shipped on September 9, 2026, adding Reverse PRIME support for multi-GPU setups along with more than 40 other fixes.

X11 is the decades-old protocol most Linux desktops still use to draw windows on screen. YSERVER's own description is direct about its goal: "provide a practical X11 server that runs real desktop environments, window managers, and applications on modern Linux while dropping legacy baggage." It is licensed under MIT.

What Reverse PRIME actually does

PRIME is the standard way Linux handles a computer with more than one graphics card, common on laptops that pair an integrated GPU with a discrete one.

Reverse PRIME flips the usual setup. A system can now render on its primary GPU and pass the finished image to a secondary GPU for display. Phoronix reports this makes multi-display configurations more flexible than the standard PRIME direction alone.

What else is in 1.5

The release notes credit the changes to several different contributors, not one person working alone.

Change	What it does
Mesa OML MSC rate queries	Lets Flatpak apps using ANGLE query frame timing correctly
DRI3 1.4 sync objects	Routes synchronization through the kernel's DRM layer
Server-side window borders	Draws window borders in the server instead of each app doing it
Vsync-off uncapping	Lets games run uncapped when vsync is off, with deferred execution
aarch64 support	Expands the architecture list alongside x86_64

The project has tested against i3, XFCE, KDE Plasma, Awesome and Compiz, and against AMD, Intel, Nvidia, Apple M1/M2 and Snapdragon X1 hardware. Its README claims Steam games run "almost on par with Xorg," the decades-old X server most Linux distributions ship by default.

The previous release, 1.4.0, shipped six weeks earlier on July 29, 2026.

Where the code came from

Phoronix's report includes a detail that stands out for this site's readers: the project "was largely developed using AI code assistance during its initial phases," specifically Claude Code.

That does not mean the project stayed a solo AI-assisted effort. The 1.5 release notes name at least three separate contributors for its headline features. The repository also requires signed commits, a standard measure against tampered code getting into a project's history. Claude Code puts its own session link in commits by default now, which is one small piece of the same trend toward AI-authored code carrying a visible trail.

What this means for developers

Treat YSERVER as an experiment worth watching, not a production Xorg replacement yet. A from-scratch reimplementation of a protocol as old and quirky as X11 will keep surfacing edge cases for a while. The project's own comparison point is "almost on par with" Xorg's gaming performance, not equal to it.

If you run a multi-GPU laptop, Reverse PRIME is the piece to test first. It targets a real, specific pain point: getting rendering and display right when the two jobs sit on different chips.

The AI-assisted origin is worth noting without over-reading it. The project started with one maintainer and AI-assisted early code. It has since reached 557 stars and 31 forks, and picked up outside contributors for this release. That is a data point about how these tools change the odds of a hobby systems project getting off the ground at all. It is not proof that AI wrote a production display server unsupervised.

If you package or ship Linux desktop software, YSERVER is still early. Filing an issue against your specific window manager or GPU combination does more good right now than switching a real desktop over to it.