Build a Linux OS that adapts across desktop, tablet, phone and TV

A small team says nearly every part of Luma, a Fedora-based Linux for desktop, tablet, phone and TV, went through Codex or Claude Code. It is out as an open source alpha.

Done withCodexClaude Code· Nov 16, 2026

What they did

u/GoodMacAuth and a small team are building Luma, a free Linux distribution meant to look and behave the same on desktop, tablet, phone and TV. They start from Fedora 44 Silverblue and fork heavily: Prairie, a shell derived from GNOME Shell that reshapes itself for each screen size; LumaUI, a GTK 4 toolkit for writing one app that adapts to every device; an app store called Depot; a set of creative apps; and an in-OS agent called Ari. The poster says the shell, the apps, the design system, the phone ports, the website and the nightly builds all went through Codex or Claude Code. The people choose what goes in, test on real hardware and send the agent back until each piece works.

How it went

Luma is available as an alpha with x86 and ARM ISOs, a Raspberry Pi 5 image and a VM build for trying it. Phone ports for the Fairphone 6, Pixel 9 and Unihertz Titan 2 Elite are in progress, much of that porting done with agents, and the poster says phone support is early and varies by device. Cross-device sync is only partly working. The post gives no figures for time, cost or team size.

Worth knowing

The team found GTK 4 a good target for agents because one app description covers every screen. They publish plain Markdown guides at simplyluma.com/agents so a reader's own agent can build apps, port phones or send fixes upstream. Commenters were sceptical about the value of yet another distro and worried about attracting low-quality agent-written contributions.

Try it

With Codex· 4 parts to fill in

Help me build [an app or feature] for [my Linux desktop or a GTK 4 project] that adapts to [desktop, tablet and phone screen sizes] from one codebase. Read the project's contributor guides first, then propose a layout for each screen size and wait for my approval. Write the code, build it, and give me exact steps to test it on [my hardware or a VM]. After I report what broke, fix it and repeat. Stop when I confirm it works on every target and show me a summary of the changes ready to send upstream.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related