# How it Works

Omega OS runs as an application-layer operating system on top of your existing OS, creating an isolated desktop environment that behaves like a full OS.

## System Architecture

Omega OS uses Electron’s multi-process architecture.

### Main Process

* Controls lifecycle
* Manages windows
* Handles system-level operations

### Renderer Processes

* Each application runs in its own isolated process
* No direct Node.js access
* Strict sandboxing

### Context Isolation

* Prevents renderer access to main process APIs

### IPC Communication

* Secure IPC via context bridge only

## Isolation Model

Omega OS implements multiple isolation layers:

* **Process Isolation:** One app per process
* **Filesystem Isolation:** Data stored only in Omega OS directory
* **Network Isolation:** Optional Tor routing
* **Memory Isolation:** Renderers cannot access main memory

## Data Storage

All user data is stored in an isolated directory:

```
~/.omega-os/isolated-env/
├── apps/
│   ├── browser/
│   ├── word/
│   ├── sheets/
│   └── wallet/
├── settings/
└── identity/
```

This prevents data leakage into the host system.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://omega-6.gitbook.io/omega/omega-os/how-it-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.