DEVELOPERS · OPEN SOURCE

Try it. Trace it.
Change it.

GenOS is a polyglot agent runtime with a Rust workspace, Node.js control plane, CLI and MCP interfaces. Start with the zero-token safe debugging example, then follow its evidence into the source.

Browse reviewed source ↗Zero-token demo ↗REST / MCP reference →
QUICK START

Run the runtime locally.

Use Rust stable 1.88+, Node.js 22.12+, Git and native C/C++ build tools. Install each workspace’s dependencies. The zero-token demo exercises local state mechanics without a model or API key; it does not prove replay of arbitrary external commands.

Full setup guide ↗
LOCAL DEVELOPMENTRUST · NODE
# Clone and install dependencies
git clone https://github.com/PISSARAW/GenOS.git
cd GenOS
git checkout 5091f70608a9305cb7bbbf5bb292d60c4c9b361e
npm ci
npm ci --prefix backend
npm ci --prefix mcp
cargo build --workspace

# Zero-token demo · Windows / cross-platform
node examples/safe-debugging-demo/run-demo.mjs target/debug/genos

# Backend · configure .env before model missions
cp .env.example .env
npm --prefix backend start
RUST 1.88+ · NODE 22.12+ · SQLITE NATIVE BUILD TOOLSDEMO CONTRACT ↗
First model mission

Start an Ollama or other configured model server and make the chosen model available before dispatch. The example environment selects Ollama but does not download a model. MCP stdio exposes no tools without GENOS_MCP_LEASE; authorize only the named tools needed by the client. Backend HTTP calls additionally require the configured credentials and tenant scope.

MCP lease and client setup ↗
PROJECT SURFACES
01Rust workspaceRuntime core and CLI↗02Node.js control planeREST, gRPC and persistence↗03MCP interfacesLocal tool access under lease↗04DocumentationArchitecture, contracts and evidence↗
Safety is part of the interface.

GenOS validates paths and tool arguments, enforces leases and uses promotion gates. Keep those boundaries in place when building integrations.