Sash is canonical
Reusable language and agent behavior belongs in sash-libs/; SashOS product behavior belongs in sashos/os/.
An evolving language and systems project
Sash is a programming language and ecosystem in active development. Product behavior is being moved into Sash itself, with explicit boundaries where a platform must provide services.
Current maturity: work in progress. The compiler and operating-system experience are not yet complete products.
01 / The project
Sash aims to make language, reusable libraries, agent behavior, and SashOS product logic readable and reviewable in Sash. Bootstrap and platform adapters support that goal; they are not substitutes for the canonical implementation.
Reusable language and agent behavior belongs in sash-libs/; SashOS product behavior belongs in sashos/os/.
The existing JavaScript bootstrap is a separately scoped path. It must not depend on or launch a Rust executable.
Explore the bootstrap repositoryFilesystem, storage, and platform effects pass through documented host capabilities rather than ambient access.
Explore SashOS support02 / How the pieces connect
The repository is a work-in-progress integration. These boundaries describe ownership and intended flow, not a claim that every target is finished or interchangeable today.
A host boundary is not a security guarantee by itself. Workload isolation, authentication, and platform support must be evaluated and accepted separately for each deployment.
03 / Evidence, not hype
These are deliberately bounded snapshots. See the project documentation for the exact support matrix and evidence attached to a specific source revision.
A JavaScript seed bootstrap, compiler foundations, and SashOS-on-WASM experiments exist. The supported language surface is bounded; this is not yet a complete self-hosted toolchain.
Sash libraries and compiler workThe checked-in local preview has a graphical browser Desktop and a VS Code experience. Current browser capabilities remain limited and device-local-first.
Visit the SashOS siteSasha's current screen is routing-oriented, not live model inference. App installation and execution are also bounded; a full app lifecycle is not accepted yet.
Review current project state04 / The operating-system project
The first hosted web direction is a local-first PWA. User state stays in the browser in this phase. GitHub sign-in and encrypted backup/sync are intentionally later work, not an implied feature.
05 / What comes next
Progress is gated by working vertical slices and repeatable evidence—not by a feature's presence in a plan or repository.
Package the SashOS source and browser host with explicit capability reporting, offline behavior, and clear recovery.
Improve the pure-Sash compiler/runtime path and keep bootstrap behavior aligned through conformance tests.
GitHub login, encrypted private backups, multi-device restore, and any remote service require a separate threat model and explicit consent.
A promise we can keep