Skip to content

OrganicOS Overview

OrganicOS is a long-running attempt to create a living, assistant-native computing environment where intelligence is part of the operating model instead of a separate app.

The current implementation is hybrid. It includes a customized Linux desktop, Organic Glass interface work, Nebula/OpenClaw assistant orchestration, local services, media and voice systems, streaming/remoting paths, Android and input-control work, and this Portal as the documentation and public-facing map.

OrganicOS is not just a themed Linux desktop and not just a chatbot panel. The project tries to reduce the hard boundaries between:

  • desktop and control center;
  • system and assistant;
  • local and remote interaction;
  • Linux, Windows-connected workflows, and Android-adjacent surfaces;
  • static UI and adaptive operating environment;
  • documentation, source, runtime state, and recovery workflow.

The practical goal is to make the environment understandable, usable, recoverable, and eventually publishable without losing the larger vision.

OrganicOS currently lives on a Linux host with a customized Plasma/X11 desktop and a growing set of local services. The desktop is important, but it is one surface of the environment rather than the whole product.

Organic Glass is the custom interface layer. It contains launcher work, panels, assistant surfaces, terminal views, media and nexus surfaces, wrappers, overlays, and visual identity experiments.

Nebula/OpenClaw form the assistant and orchestration layer: memory, skills, local tools, system mapping, command flow, voice paths, and service awareness. This is the layer that makes the system assistant-native instead of merely assistant-adjacent.

Moonlight/Supernova, Apollo-related work, Input Nebula, ADB, scrcpy, Input Leap, and Android runtime experiments are part of the operating model. OrganicOS is designed to be used across screens, devices, remoted sessions, and mixed input paths.

The Portal is the public map. It turns scattered local source trees, notes, service evidence, visual assets, and release planning into one navigable website.

  • The Portal has public pages for About, Developers, Gallery, Support, Downloads, Community, and Documentation.
  • The documentation system is structured with Concepts, Operations, and Reference sections.
  • The public GitHub profile is linked from the About and Developers pages.
  • The repository map and cleanup plan define the current publishing path.
  • Canonical repository selection.
  • Public/private redaction boundaries.
  • Installation and packaging docs.
  • Service and command references.
  • Release artifacts and checksums.
  • Contributor workflow and community links.

Treat this page as the current public overview, not a final product specification.