The Web Kernel

Made with ❤️ by Jay Mathis

ecmaOS is a browser-based operating system kernel and suite of applications written primarily in TypeScript, AssemblyScript, and C++. It's the successor of web3os.

The goal is to create a kernel and supporting apps that tie together modern web technologies and utilities to form an "operating system" that can run on modern browsers, not just to create a "desktop experience". It offers the ability to run a wide variety of apps on top of an already (mostly) sandboxed foundation, offering some measure of security by default as well as rich developer tooling. Its main use case is to provide a consistent environment for running web apps, but it has features that allow for more powerful custom scenarios, such as a platform for custom applications, games, and more.

---

"The computer can be used as a tool to liberate and protect people, rather than to control them." — Hal Finney

Features

• TypeScript, WebAssembly, AssemblyScript, Rust, C++
• Filesystem supporting multiple backends powered by zenfs
• Terminal interface powered by xterm.js
• Pseudo-streams, allowing redirection and piping
• Device framework with a common interface for working with hardware: WebBluetooth, WebSerial, WebHID, WebUSB, etc.
• Some devices have a builtin CLI, so you can run them like normal commands: # /dev/bluetooth
• Install any client-side npm package (this doesn't mean it will work out of the box as expected)
• Event manager for dispatching and subscribing to events
• Process manager for running applications and daemons
• Interval manager for scheduling recurring operations
• Memory manager for managing pseudo-memory: Collections, Config, Heap, and Stack
• Storage manager for managing Storage API capabilities: IndexedDB, localStorage, etc.
• Internationalization framework for translating text powered by i18next
• Window manager powered by WinBox
• BIOS: A C++ module compiled to WebAssembly with Emscripten providing performance-critical functionality
• Jaffa: A Tauri app for running ecmaOS in a desktop or mobile environment
• Metal: An API server for allowing connections to physical systems from ecmaOS using Hono
• SWAPI: An API server running completely inside a service worker using Hono

Basic Concepts

Apps

/apps

• These are full applications that are developed specifically to work with ecmaOS
• Refer to the full list of official published apps on npm
• See the APPS.md file for a list of community apps; submit a PR to add your app!
• An app is an npm package, in which the bin file has a shebang line of #!ecmaos:bin:app:myappname
• Its default export (or exported main function) will be called with the ProcessEntryParams object
• They can be installed from the terminal using the install command, e.g. # install @ecmaos-apps/code
• Run the installed app (bins are linked to /usr/bin): # code /root/hello.js
• During development, it can be useful to run a Verdaccio server to test local packages
• To publish to Verdaccio, run # npm publish --registry http://localhost:4873 in your app's development environment
• Then to install from your local registry, run # install @myscope/mypackage --registry http://localhost:4873

BIOS

/core/bios

• The BIOS is a C++ module compiled to WebAssembly with Emscripten providing performance-critical functionality
• The BIOS has its own filesystem, located at /bios — this allows data to be copied in and out of the BIOS for custom code and utilities
• The main idea is that data and custom code can be loaded into it from the OS for WASM-native performance, as well as providing various utilities
• Confusingly, the Kernel loads the BIOS — not the other way around

Commands

/core/kernel/src/tree/lib/commands

• Commands are small utilities that aren't quite full Apps, provided by the shell
• Some builtin commands that exist now will be moved into separate apps over time

Devices

/devices

• Refer to the full list of official devices on npm
• See the DEVICES.md file for a list of community devices; submit a PR to add your device!
• Devices get loaded on boot, e.g. /dev/bluetooth, /dev/random, /dev/battery, etc.
• A device can support being "run" by a user, e.g. # /dev/battery status
• Devices may also be directly read/written using fs methods, and will behave accordingly (or have no effect if not supported)
• An individual device module can provide multiple device drivers, e.g. /dev/usb provides /dev/usb-mydevice-0001-0002

Generators

/turbo/generators

• Generators are used to scaffold new apps, devices, modules, etc.
• They are located in the turbo/generators directory of the repository
• They are used by the turbo gen command, e.g. turbo gen app, turbo gen device, turbo gen module, etc.

Jaffa

/core/jaffa

• Jaffa is a Tauri wrapper for the ecmaOS kernel
• It's used to tie the kernel into a desktop or mobile environment, allowing for native functionality

Kernel

/core/kernel

• The kernel ties together the various components of the system into a cohesive whole
  • Authentication (WebAuthn)
  • Components (Web Components/Custom Elements)
  • Devices
  • DOM
  • Events (CustomEvents)
  • Filesystem (ZenFS)
  • Internationalization (i18next)
  • Interval Manager (setInterval)
  • Log Manager (tslog)
  • Memory Manager (Abstractions)
  • Process Manager
  • Protocol Handlers (web+ecmaos://...)
  • Service Worker Manager
  • Shell
  • Storage (IndexedDB, localStorage, sessionStorage, etc.)
  • Terminal (xterm.js)
  • User Manager
  • WASM Loader
  • Window Manager (WinBox)
  • Workers (Web Workers)

Metal

/core/metal

• Metal is an API server for allowing connections to physical systems from ecmaOS using Hono
• Authenticated and encrypted connections with JWK/JWE/JOSE

Modules

/modules

• Refer to the full list of official modules on npm
• See the MODULES.md file for a list of community modules; submit a PR to add your module!
• Modules are dynamically loaded into the kernel at boot and can be enabled or disabled
• They are specified during build via the VITE_KERNEL_MODULES environment variable
  • e.g. VITE_KERNEL_MODULES=@ecmaos-modules/[email protected],@your/[email protected]
• Versions must be pinned and are mandatory - you cannot use NPM version specifiers
• They can provide additional functionality, devices, commands, etc.
• They offer a common interface for interacting with the kernel
• Generally they should be written in AssemblyScript, but this isn't required

Packages

• Packages are NPM packages that are installed into the ecmaOS environment
• They can be installed from the terminal using the install command, e.g. # install jquery
• NPM version specifiers are supported, e.g.:
  • # install [email protected]
  • # install jquery@^3.7.1
  • # install jquery@latest
• JSR may be used with the NPM compatibility layer:
  • # install @jsr/defaude__hello-jsr --registry https://npm.jsr.io

SWAPI

/core/swapi

• The SWAPI is an API server running completely inside a service worker using Hono
• It allows for various operations including the fs route to fetch files via URL
• e.g., # fetch /swapi/fs/home/user/hello.txt
• e.g., # fetch /swapi/fake/person/fullName

Utils

/utils

• Utilities and configuration used during development

Important Files and Directories

• /bin/: Built-in commands
• /bios/: The BIOS filesystem
• /boot/init: A script that runs on boot
• /dev/: All devices are here
• /etc/packages: A list of installed packages to load on boot
• /home/: Contains user home directories
• /proc/: A directory containing various dynamic system information
• /root/: The home directory for the root user
• /usr/bin/: Executable packages get linked here
• /usr/lib/: All installed packages are here
• /var/log/kernel.log: The kernel log

Command Examples

ai "Despite all my rage" # use `env OPENAI_API_KEY --set sk-`
cat /var/log/kernel.log
cd /tmp
echo "Hello, world!" > hello.txt
chmod 700 hello.txt
chown user hello.txt
clear
cp /tmp/hello.txt /tmp/hi.txt
download hello.txt
edit hello.txt
env hello --set world ; env
fetch https://ipecho.net/plain > /tmp/myip.txt
fetch /xkcd-os.sixel # xterm.js includes sixel support
fetch /swapi/fs/home/user/hello.txt # fetch a file from the filesystem
fetch /swapi/fake/person/fullName # fetch a random person from the SWAPI
install jquery
install @ecmaos-apps/boilerplate
ls /dev
mkdir /tmp/zip ; cd /tmp/zip
upload
mount myuploadedzip.zip /mnt/zip -t zip
cd .. ; pwd
unzip zip/myuploaded.zip
mv zip/myuploaded.zip /tmp/backup.zip
passwd old new
play /root/test.mp3
ps
rm /tmp/backup.zip
screensaver
snake
stat /tmp/hello.txt
touch /tmp/test.bin
umount /mnt/zip
user add --username user
su user
video /root/video.mp4
zip /root/tmp.zip /tmp

Device Examples

/dev/audio test
/dev/battery status
/dev/bluetooth scan
echo "This will error" > /dev/full
/dev/gamepad list
/dev/geo position
/dev/gpu test
/dev/hid list
/dev/midi list
echo "Goodbye" > /dev/null
/dev/presentation start https://wikipedia.org
cat /dev/random --bytes 10
/dev/sensors list
/dev/serial devices
/dev/usb list
/dev/webgpu test
cat /dev/zero --bytes 10 > /dev/null

Note: many device implementations are incomplete, but provide a solid starting point

Code Execution Example

echo "window.alert('Hello, world!')" > /root/hello.js
load /root/hello.js

App Development

The apps directory in the repository contains a number of examples of how to develop apps, but there are many approaches you could take.

• @ecmaos-apps/boilerplate: A minimal boilerplate app for developing new apps
• @ecmaos-apps/code: A simple code editor app using Monaco; serves as a good reference for more complex apps

Basically, your app's bin file has a main (or default) function export that is passed the kernel reference and can use it to interact with the system as needed. A shebang line of #!ecmaos:bin:app:myappname is required at the top of the bin file to identify it as an app.

Early Days

The kernel is currently in active development. It is not considered stable and the structure and API are very likely to change in unexpected and possibly unannounced ways until version 1.0.0. Use cautiously and at your own risk.

Things to keep in mind:

• Things have changed a lot since the tests were written, so they need to be updated and fixed
• The kernel is designed to be run in an environment with a DOM (i.e. a browser)
• Many features are only available on Chromium-based browsers, and many more behind feature flags
• There will be a lot of technical challenges to overcome, and many things will first be implemented in a non-optimal way
• Command interfaces won't match what you might be used to from a traditional Linux environment; not all commands and options are supported. Over time, Linuxish commands will be fleshed out and made to behave in a more familiar way.
• Globbing doesn't work in the terminal yet, but is supported at the filesystem level

Development

Turborepo is used to manage the monorepo, and pnpm is used for package management.

A good place to start is viewing the scripts property of package.json in the root of the repository.

# Clone
git clone https://github.com/ecmaos/ecmaos.git

# Install dependencies
cd ecmaos && pnpm install

# Run the dev server
pnpm run dev:kernel

# Run the docs server (optional)
pnpm run dev:docs

# Build
pnpm run build

# Run tests
pnpm run test
pnpm run test:watch
pnpm run test:coverage
pnpm run test:bench
pnpm run test:ui

# Generate modules
turbo gen app # generate a new app template
turbo gen device # generate a new device template
turbo gen module # generate a new module template

Also see turbo.json and CONTRIBUTING.md for more information.

Security Vulnerabilities

If you find a serious security vulnerability, please submit a new Draft Security Advisory or contact the project maintainer directly at [email protected].