PaOS · 0.1 Preview simulator PaOS 0.1 — as it will look on hardware Offline browser reference · simulated files, services and accounts
×
A preview of PaOS 0.1
The desktop is familiar. What it can do is new.
Pick a short, hands-on glimpse of PaOS. Each opens a working part of this simulator, with sample data and visible controls.
From power on Watch it boot See PaOS 0.1 start: the boot manager, the boot log and the desktop it lands on. Watch it boot → Linux and Claude Linux and Claude in the Terminal Open a Linux guest from the PaOS Terminal and ask a scripted Claude session to build a small app. Open the Terminal → The app model Apps are scripts A PaOS app is a script with forms and grants. See the verbs it sends and how its forms are checked. Explore Scripts & recipes →
Want the basics? Explore the desktop Interactive design simulator · sample data · native features still being qualified
Help improve this preview? With your choice, we count which sample apps are viewed and used. We do not record what you type or your simulated files.
Share basic usage No thanks What is recorded? If you agree, Google Analytics receives page visits, broad device information, scene changes, app views and opens, app focus and close counts, and broad categories of activated controls. It may use cookies and process network information under Google's terms. You can withdraw below. No email address, typed text, file name, URL, click coordinates or simulated content is sent as an event.
Install PaOS now
PaOS-tech
PaOS open source
Invite a beta tester
PaO S FORGE Install opens a simulator preview. Public downloads and source code are not yet available.
Try this in the simulator Dismiss guide
The simulator requires Canvas and JavaScript. Exit desktop view
Icons: double-click to open · Drag to arrange · Right-click for options · Menu: Shift+F10 Choose a language Usage choice Session usage report This report counts sample-app views, launches, focus changes, activated controls and closes in this browser tab only. It is not a report of real PaOS use. Recording starts only when you choose it; export is a local download.
Record this session Export JSON Clear report Recording paused · 0 events in this tab
App Views Launches Focuses Actions Closes
Choose a language
Choose one of six planned PaOS languages. Interface controls change now; sample web pages and documents keep their original language.
Continue in English
PaOS looks better on a larger screen
The desktop simulator is designed for a laptop or desktop. Emailing a link is not available yet, so open this page on a computer or continue here.
Try it on this screen
Invite someone to the PaOS beta
Enter their details to preview an invitation. This local test saves nothing and sends no email. Later, each invitee will receive a unique temporary password.
0.1 at RC on hardware
Known differences from real hardware Close This view uses PaOS's own colours, metrics and fonts. It is still a browser drawing, not evidence about real machines.
Assumptions: looks not decided yet
Where the 0.1 look is not decided, this view draws the most likely native rendering. Each one is an open question.
Working paper preview · English draft · October 2026
One core, many faces × A different desktop can feel like a different operating system. It does not have to become a different application target.
Wallpaper Changes the backdrop.
Theme Changes visual language and shared controls.
Edition Changes the shell and chosen apps while preserving the PaOS core and app contract.
Fork Changes the core or a compatibility promise and takes on its own maintenance burden.
The distribution problem
When desktop environments, package formats, library versions, release policies and support promises diverge, an app maker must choose which combinations to build, test and maintain. Linus Torvalds has discussed fragmentation as a barrier for desktop Linux. That does not make visual choice the problem: the costly part is repeatedly negotiating incompatible software and support targets.
Other forces matter too, including existing user habits, hardware and OEM availability, application supply and marketing. Fragmentation is a plausible contributor, not a complete explanation for desktop Linux adoption.
The author’s opportunity-cost hypothesis
The cumulative opportunity lost to desktop fragmentation might be measured in billions of dollars across decades. This is a research hypothesis, not a measured estimate and not a claim made by Torvalds. The paper still needs a defensible counterfactual and data before putting a number in its conclusion.
How the paper could test it
Define the market, time period and counterfactual adoption path. Separate packaging and compatibility cost from hardware, OEM, application and user-inertia effects. Estimate ranges for missed app investment, support cost and adoption, avoiding double counting. Show sensitivity to assumptions and identify cases where distro variety created value. The PaOS proposal
PaOS aims for one maintained core and update stream, an openly specified app and verb contract, and independently selectable editions that change the experience above that contract. The same app should not need a different port for each wallpaper, theme or curated desktop. Realizing that goal still requires compatibility tests, secure updates, dependency rules and evidence on actual hardware. The simulator demonstrates the distinction; it does not prove native compatibility.
Sources and starting points: the author’s “paos distros?” DS note (September 16, 2026), PaOS’s October 1 editions ruling and version-divergence discussion; Torvalds’s TFiR interview on desktop fragmentation ; and his IEEE Spectrum interview on other adoption factors. This preview is local working copy, not the finished paper.
This simulator evaluates modeled interactions. Native PaOS qualification and matched Windows Terminal fidelity remain separate.