System76's COSMIC Epoch 1.8 arrives two weeks after 1.7 with tablet grab and Bluetooth renaming

System76 has released COSMIC Epoch 1.8, the newest iteration of its Rust-built desktop environment, landing just two weeks after Epoch 1.7. Phoronix reported the release on September 10, 2026, and a Tech AI Wire write-up republished on dev.to examines both the changes and a gap between third-party coverage and System76's own release notes.

COSMIC is System76's from-scratch desktop environment for Pop!_OS, written in Rust on top of the Iced GUI toolkit rather than forking GNOME or KDE Plasma. It is also made available to other Linux distributions.

What's new in Epoch 1.8

According to Phoronix, the release carries three changes users will notice:

• XWayland windows — older applications that run through a compatibility layer instead of speaking Wayland natively — can now start minimized via the COSMIC Compositor rather than always opening on screen.
• COSMIC Shell improves tablet support, including the option to grab a graphics tablet, meaning it can take exclusive control of the device's input.
• COSMIC Settings now allows a connected Bluetooth device to be renamed, so users are no longer limited to whatever default name the hardware reports.

Two weeks between minor releases

That turnaround is remarkably short for a desktop environment. GNOME and KDE Plasma operate on release cycles measured in months, so a fortnight between point releases signals how quickly COSMIC, a comparatively young project, is iterating.

The official changelog is still pending

The GitHub release page for epoch-1.8.0 currently tells a narrower story. As of the Tech AI Wire report, System76 flags the release as a pre-release and lists its changelog as "pending." The visible text describes translation work and dependency refreshes across many COSMIC components, without the feature-level detail Phoronix published. The page has drawn 21 community reactions so far.

The two accounts do not so much contradict each other as sit out of sync: the third-party report names specific features while the vendor's notes have not been written up yet. Both can hold if System76 simply has not finished documenting the release, which the "pending" label implies.

What developers should check

Tech AI Wire flags several implications for anyone building on or packaging for COSMIC:

• Tools that read Bluetooth device names from the desktop can no longer assume the displayed name matches the hardware default.
• Applications that depend on XWayland window state should be tested under minimized startup. The change most likely honors window-manager hints that apps already emit, so no new code should be required, but verification is cheap.
• Packagers targeting Pop!_OS or other COSMIC-based distributions should treat 1.8 as a routine dependency update, rebuilding against it before assuming their packages still work, since the reported dependency changes span much of the codebase.

For the authoritative feature list, the epoch-1.8.0 release page is the reference to watch once System76 completes the changelog. Relying on a third-party summary alone is risky while the official notes remain incomplete, since summaries can be revised or expanded after the fact.

Why it matters

The headline detail is the pace. A Rust-native desktop environment shipping a minor release a fortnight after the last one is moving far faster than the established GNOME and KDE cycles, and that momentum matters for a project trying to become a credible third option in the Linux desktop space. COSMIC is also the default interface for Pop!_OS, so its maturation affects System76's entire user base and, increasingly, other distributions that adopt it.

The release also illustrates a smaller, practical lesson for anyone tracking fast-moving software: the most detailed account of what shipped came from Phoronix rather than the vendor, because the official changelog was still unfinished. Anyone basing build or packaging decisions on release notes should be aware that the two sources currently describe the same release at different levels of detail, and neither is necessarily wrong.