LeafdeckOS is our own Linux operating system, and Claude shapes it around the person using it. Connect a Claude Pro or Max account, describe how you work, and Claude builds the apps, layouts, and routines you need right into the desktop. Your data stays on your machine.
Windows and macOS are made for everyone, so nobody gets exactly what they need. Claude sits on top of them as a chat box in a corner, and it only sees what you paste in. We wanted one computer where Claude is part of the system: it can see your windows, work in your files and apps, and build the tool you're missing instead of waiting for someone to sell it.
So we built the whole stack: the operating system image, the desktop, and the apps on top of it. It runs on your own Claude plan through Claude Code, with no API key, no Leafdeck account, and no server in the middle.
On Windows, macOS, or a standard Linux desktop like GNOME or KDE, every app draws its own window its own way, and Wayland rightly stops one program from reading another. An AI assistant there has to work from screenshots: take one, guess where to click, take another.
LeafdeckOS is built differently. Nearly everything on screen belongs to one Chromium app, and Chromium already describes every window to screen readers. Claude reads that same description through Chromium's own debugger: every button, field, and line of text, each with an ID it can click. Because it reaches it from inside Leafdeck, nothing gets around Wayland's rules.
Regular Linux apps from Flathub still work. They're drawn by GTK or Qt, so for those Claude falls back to screenshots, like anywhere else.
Estimates, compared with a screenshot-based computer-use tool on Windows or macOS.
Turn on Claude Code control and Claude gets tools built into the OS: list the open windows, read any of them as an outline, click, type, scroll, and take screenshots. That covers websites and Settings too. A badge in the menu bar shows when it's working.
Claude writes the app, opens it, and checks its own work with screenshots. Each app runs in its own sandbox, asks before using your data, and saves a version before every change so you can restore it in one click.
Designer captures any element from any window, with its hover, focus, and pressed states, as editable layers. One button writes the hand-off for HTML and CSS, React, React and Tailwind, Vue, Svelte, a web component, or a LeafdeckOS app. Graphic Designer handles vector artwork.
Clients, Pipeline, Invoices, Time Tracker, Finance, Calendar, and Tasks, with widgets for inboxes, the agenda, today's tasks, and the timer. Claude reads all of it directly as data when you ask a question.
Terminals and Claude sessions run in a system service, not inside a window. Restart the desktop and the work is still going, with its output intact. Claude can set up and run the routines you repeat.
Suggestions only, ask before each step, work only on the apps it builds for you, or operate the whole desktop. You can step back down at any time, and anything that needs administrator rights still asks for your password.
LeafdeckOS is my everyday computer. I'm a designer, a developer, and a business owner, often in the same hour, and nothing off the shelf fit all three. So I asked Claude to build the environment I needed, piece by piece.
It runs on a Lenovo Yoga Book 9: two touch screens and an external monitor, hardware Linux barely supported. Claude got the speakers working, made touch follow each screen, and wired up the function keys the system ignored. The OS fits the machine, not the other way around.
LeafdeckOS covers most of what we offer clients: a CRM, invoicing, sandboxed apps, design-to-code tooling, and AI that works with your real data instead of screenshots of it. When your project needs one of those, we've already built it once for ourselves.
Tell us what you're trying to build. We'll show you how we'd approach it.