Project Overview

About OrganicOS

OrganicOS is a local-first, assistant-native Linux distribution project with a real release-candidate ISO, plus the live desktop, services, documentation, automation, streaming, device control, and release planning around it.

OrganicOS

A Linux distro built from the live system, documented one verified piece at a time.

OrganicOS is not only a themed Linux setup or a development environment. It is an installable Linux distribution effort, currently represented by an OrganicOS 24.04 release-candidate ISO, and an attempt to make intelligence structural inside the operating system itself.

The Portal is the front door for that work. It gathers project maps, documentation, support notes, developer references, downloads, visual assets, and release planning so the live Linux distro image, Nebula tooling, Organic Glass, streaming/control paths, and public cleanup work can be understood together.

Open GitHub Profile View Gallery

GitHub

Public profile for OrganicOS-related repository cleanup, forks, and future project publishing.

https://github.com/zain1806481

What It Connects

The current system is a collection of working layers being consolidated into a clearer Linux distro story, a safer ISO release process, and a public documentation path.

Distro

Installable Linux Distribution

OrganicOS is being built as a real Linux distro image, with an OrganicOS 24.04 release-candidate ISO already produced from the live system.

Core Idea

Assistant As Infrastructure

Nebula, OpenClaw, memory, tools, voice, and system mapping are treated as part of the operating environment, not a side chat window.

Interface

Organic Glass Surface

The Electron-based shell collects panels, launchers, media views, terminal surfaces, assistant tools, wrappers, and overlay work into one visual layer.

Runtime

Hybrid Operation

Streaming, Moonlight/Supernova, Android control, input sharing, and local web services are part of how the system is actually operated.

Principle

Local-first

Run the useful system close to the machine and expose only the paths that are intended to be public.

Principle

Verified docs

Document from inspected source, service files, runtime checks, and project notes instead of guessing.

Principle

One environment

Treat desktop, assistant, media, devices, remoting, and docs as connected parts of the same operating model.

Principle

Public release carefully

Publish after source cleanup, redaction review, build validation, and a clear GitHub story.