LotusOS is a custom Debian-based Linux live/installable ISO with a Tauri + React + Rust shell called Lotus Shell. It boots into KDE Plasma, autostarts Lotus Shell, and includes a Calamares installer that has been verified on disposable VirtualBox VDIs. The current preview is a source-and-docs milestone for a local-first workspace OS, not a production hardware release.
LotusOS explores how to turn a normal Linux base into a focused, calm, local-first workspace OS without writing a custom kernel or bootloader from scratch. Instead of leaving users in a generic desktop with scattered entry points, it adds a first-run home surface, local system context, app launchers, and bounded project and resource areas on top of a standard Debian + KDE base.
| Screenshot | Evidence |
|---|---|
| Live desktop | ![]() |
| Home dashboard | ![]() |
| Settings overview | ![]() |
| Installer completion | ![]() |
Installed-system boot, SDDM, and post-login Lotus Shell were manually verified for Phase 5F, but no additional installed-desktop screenshot is curated in this README set.
- Build the ISO through Debian
live-build. - Boot the ISO in VirtualBox.
- KDE Plasma starts in the live session.
- Lotus Shell autostarts.
- Calamares can install the image to a disposable VDI.
- The installed system boots into SDDM and Plasma.
- Lotus Shell autostarts again after installed login.
- Debian-based live ISO
- KDE Plasma desktop
- Lotus Shell autostart
- Polished Home dashboard
- Read-only system snapshot
- Settings system overview
- Local app launcher surface
- Local resource and project cards
- Calamares installer integration
- Disposable VDI install verification
- Local-first scope
- No bundled AI credentials
flowchart TD
A[Debian live-build] --> B[LotusOS ISO]
B --> C[KDE Plasma live session]
C --> D[Lotus Shell autostart]
D --> E[Tauri shell]
E --> F[React UI]
E --> G[Rust backend commands]
B --> H[Calamares installer]
H --> I[Disposable VDI install]
I --> J[Installed LotusOS desktop]
- Debian
live-build - KDE Plasma
- Calamares
- Tauri
- React
- TypeScript
- Rust
- VirtualBox verification
Use Linux or WSL2 Ubuntu for ISO work. The OS build scripts are Bash scripts and are not intended to run directly in PowerShell.
sudo apt update
sudo apt install live-build qemu-system-x86 xorriso isolinux syslinux-common squashfs-tools
sudo apt install nodejs npm cargo rustc libgtk-3-dev libwebkit2gtk-4.1-dev librsvg2-devIf the distro Rust toolchain is too old for the Tauri packaging path, install a current stable Rust toolchain with rustup.
git clone https://github.com/ChimdumebiNebolisa/LotusOS.git
cd LotusOScd shell/lotus-shell
npm installcd shell/lotus-shell
npm run buildcd shell/lotus-shell/src-tauri
cargo check
cd ..
npm run tauri build -- --no-bundleRepository-root dependency check:
bash os/scripts/build-iso.sh --checkBuild the ISO:
bash os/scripts/build-iso.shWSL root build with user rustup paths exported:
wsl.exe -u root -- /usr/bin/bash -c 'export CARGO_HOME=/home/<user>/.cargo RUSTUP_HOME=/home/<user>/.rustup PATH="/home/<user>/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"; cd /mnt/c/Users/Chimdumebi/LotusOS && bash os/scripts/build-iso.sh'wsl.exe -u root -- /usr/bin/bash os/scripts/verify-iso-contents.shPrimary supported VirtualBox lane:
- OS type: Debian 64-bit
- RAM:
4096 MB - CPUs:
2 - VRAM:
128 MB - Graphics controller:
VMSVGA - 3D acceleration:
on
Optional QEMU smoke boot:
bash os/scripts/test-qemu.sh artifacts/lotusos-amd64.isocd shell/lotus-shell && npm run buildcd shell/lotus-shell/src-tauri && cargo checkcd shell/lotus-shell && npm run tauri build -- --no-bundlewsl.exe -u root -- /usr/bin/bash os/scripts/verify-iso-contents.sh- VirtualBox live ISO verification
- Disposable VDI install verification
- VirtualBox graphics and session instability has appeared in some timed runs, even in the supported
VMSVGA+ 3Donlane. - Hardware installation is not verified.
- ISO and VDI artifacts are not committed to git.
- AI Hub is placeholder/local-first only.
- No cloud sync or auth.
- No production release guarantees.
- Phase 5F installed-system verification is manually verified after an automated Calamares run was blocked by a live-session lock.
MIT. See LICENSE.



