PhreshOS/system

The PhreshOS server, desktop, and authoritative system runtime.

TypeScript

1

343 commits

updated Sep 30, 2026

See the code

See what people are saying

SourceMessageScoreDate

i spent 6+ months building an actual OS for web apps (r/SideProject)

so for the past 6 months or so i've been trying to build a real operating system for web apps the idea is pretty simple. it's a real, programmable system with a web desktop you can reach from anywhere, but the apps on it are built with normal web tools. what's new is that you build the app inside…

2

Sep 30, 2026

README

PhreshOS System

The authoritative runtime and web desktop for PhreshOS Programs.

Documentation · Runtime model · Installation · Source

Role

The System owns Program and Process lifecycle, Endpoint execution, routing, authentication, persistence, permissions, host capabilities, and the web Desktop that represents this state.

The browser is a display, not the authority. Client, Server, Node, and CLI consumers reach one shared domain model whose contracts are defined by Core. See What is PhreshOS? for the complete product model.

Installation

The current System requires Node.js 24.15.0 or newer. Install and operate it through the CLI:

phresh system install
phresh system status
phresh system start
phresh system stop
phresh system enable
phresh system disable

Production state uses ~/.phreshos by default. PHRESHOS_HOME selects another System home. See Installation for the complete host and service workflow.

Development

bun install --frozen-lockfile
bun run verify
bun run dev

Build or package the production release with:

bun run build
bun run pack

verify checks the source contracts and validates the packed System from a clean installation.

check performs static checks, build creates distributable output, and test runs Vitest assertions from tests/. Run build before testing built artifacts. verify runs check, build, and test in order. Operational tooling belongs in scripts/; tests and their fixtures belong in tests/. Verification uses the committed dependency graph without local package substitutions.

Contributing

See CONTRIBUTING.md for the repository workflow and SECURITY.md for private vulnerability reporting.

License

Licensed under the MIT License. Copyright © 2026 Zohayr SLILEH.

PhreshOS/system

The PhreshOS server, desktop, and authoritative system runtime.

TypeScript

1

343 commits

updated Sep 30, 2026

See the code

See what people are saying

SourceMessageScoreDate

i spent 6+ months building an actual OS for web apps (r/SideProject)

so for the past 6 months or so i've been trying to build a real operating system for web apps the idea is pretty simple. it's a real, programmable system with a web desktop you can reach from anywhere, but the apps on it are built with normal web tools. what's new is that you build the app inside…

2

Sep 30, 2026

README

PhreshOS System

The authoritative runtime and web desktop for PhreshOS Programs.

Documentation · Runtime model · Installation · Source

Role

The System owns Program and Process lifecycle, Endpoint execution, routing, authentication, persistence, permissions, host capabilities, and the web Desktop that represents this state.

The browser is a display, not the authority. Client, Server, Node, and CLI consumers reach one shared domain model whose contracts are defined by Core. See What is PhreshOS? for the complete product model.

Installation

The current System requires Node.js 24.15.0 or newer. Install and operate it through the CLI:

phresh system install
phresh system status
phresh system start
phresh system stop
phresh system enable
phresh system disable

Production state uses ~/.phreshos by default. PHRESHOS_HOME selects another System home. See Installation for the complete host and service workflow.

Development

bun install --frozen-lockfile
bun run verify
bun run dev

Build or package the production release with:

bun run build
bun run pack

verify checks the source contracts and validates the packed System from a clean installation.

check performs static checks, build creates distributable output, and test runs Vitest assertions from tests/. Run build before testing built artifacts. verify runs check, build, and test in order. Operational tooling belongs in scripts/; tests and their fixtures belong in tests/. Verification uses the committed dependency graph without local package substitutions.

Contributing

See CONTRIBUTING.md for the repository workflow and SECURITY.md for private vulnerability reporting.

License

Licensed under the MIT License. Copyright © 2026 Zohayr SLILEH.

Languages

TypeScript

98.7%

JavaScript

1.2%