Assistant-native operating environment
OrganicOS
A live project for turning the desktop, assistant, services, media, streaming, device control, documentation, and release workflow into one coherent computing environment. OrganicOS is also an installable Linux distribution with a 24.04 release-candidate ISO and a WSL2 importable rootfs.
Built From The Live System
OrganicOS is already running as a hybrid desktop, assistant, web, voice, media, streaming, and device-control workspace. The Portal is the public map for making that work understandable.
What OrganicOS Is
A living, assistant-native computing environment that joins the desktop, services, documents, voice, streaming, and device-control work into one system.
CreatorDeveloper Profile
The builder-facing entry point for Shane, the OrganicOS source map, public GitHub profile, and the current handoff plan.
DocsDocumentation
A reviewed knowledge base for the system model, operations, repository cleanup, command references, and release-safe documentation.
System Layers
The current work is not one app. It is a stack of surfaces and services that need to be documented, cleaned up, and published carefully.
Organic Glass
The custom interface layer: panels, launcher, assistant surfaces, terminal, media tools, overlays, and desktop-adjacent workflow surfaces.
AssistantNebula and OpenClaw
The assistant and orchestration layer that carries memory, tools, local reasoning, voice paths, service awareness, and system mapping.
TransportStreaming and Device Control
The remoting, capture, Moonlight/Supernova, Android, ADB, scrcpy, Input Nebula, and cross-device control work that makes the system usable beyond one screen.
PublishingPublic Website
This Portal is becoming the clean public front door while private runtime details, credentials, local addresses, and unfinished artifacts stay out of release material.
Interested In OrganicOS?
Developers who want to follow the project or talk about contributing should create an OrganicOS profile and use the Community Portal. Please do not email Shane or use GitHub for direct contact; keep project conversations inside the portal.