KINGAI OS Desktop

Version and status

Version 0.1.0-dev, published October 6, 2026, amd64, with the KDE Plasma 6 desktop. It is a developer preview and is not certified for a primary workstation, so keep your daily machine as it is and test this in a VM.

What is included

• KDE Plasma 6 desktop and general-purpose Linux applications, per the release notes
• No mandatory KINGAI account, and no bundled KINGAI agent or model
• Local AI tools are yours to pick and install; the system does not choose for you
• A matching .sha256 checksum file published alongside the ISO

Positioning: your everyday computer, your rules

Desktop is the edition closest to everyday use: install it and you have a working Linux desktop for office tasks, browsing and development. The product tagline is blunt about the deal — Your Linux. Your rules. AI-ready when you choose. In practice that means three things. No KINGAI account is required to install or use it. AI tools are yours to install or skip; nothing is preinstalled and nothing picks for you. Your data stays on the machine, and the preview bundles no KINGAI agent and no model.

It also shares one Linux base with the other three editions. The editions differ through their profiles — which packages, which defaults, desktop or services, how far driver support goes — not through four separately forked codebases. A fix in the shared base lands everywhere at once, and no edition quietly rots on its own branch. On the upstream question, the product documents name Debian 13 as the recommended candidate, while stating plainly that the actual upstream of 0.1.0-dev has not been verified from the published files. This page repeats that as written.

The main features, one at a time

KDE Plasma 6 desktop

The release description for the preview is a KDE Plasma 6 desktop with general-purpose Linux applications. If you have never used KDE, expect familiar desktop habits: a bottom panel, an application menu, tiling windows, virtual desktops and full keyboard shortcuts. For the exact application set, trust the release notes and what you see in the VM over any list this page could print.

No account binding

Installing and using the system never asks you to register a KINGAI account, and no companion cloud service is waiting for you to sign in. If KINGAI.WORK services ever integrate, they will be separately authorized options, not cargo inside the system image.

Local AI tools, your choice

The preview preinstalls no KINGAI agent and no model. If you want local models, you pick the tooling and manage model sources and licenses yourself. If you do not, it is simply a clean desktop with nothing idling in the background waiting to be summoned.

Checksum published alongside

The ISO ships with a matching .sha256 file on the same release page. Run sha256sum -c in the download folder before you mount anything. One boundary the publisher states in its own docs, repeated here: a matching hash proves the bytes are unchanged. It is not a code signature, and it does not prove the build environment was trustworthy.

Good first uses

• Trying a Linux desktop: install it in a VM first, live with KDE for a few days, then decide about bare metal
• A second environment for development: an isolated test desktop with your own toolchain, kept apart from your main system
• A home for local AI tools: install them at your own pace, with compute and data never leaving the machine

What still stands between this and a stable release

The uncomfortable part, up front. Install certification has not passed: an unattended-install experiment completed partitioning, the base system and the bootloader, but ran out of time before verifying a reboot from the installed disk alone, and a corrected test is being run separately. Until that evidence exists, the official guidance is virtual machines first.

• The images carry no code signature yet, and there is no SBOM or third-party license review conclusion
• Automated install validation across UEFI/BIOS, hardware and hypervisors is unfinished; what has been verified is that both ISOs download in full and match their catalog hashes byte for byte
• Update and rollback have no drill evidence, so the preview makes no verified-upgrade claim
• No formal system requirements have been published. The 4 GB RAM / 40 GB disk figures in the product documents are validation-target candidates, explicitly not to be advertised as minimums; the only concrete numbers available are the install guide's suggested VM test setup (4 vCPU, 8 GiB RAM, 64 GiB virtual disk), which is a test setup, not a threshold

Read the install guide →　Go to downloads →　Report problems (GitHub Issues) →　Read the security page →