Features

From arriving to a terminal on your own laptop, in a browser tab, inside a minute, with nothing typed first. Everything else is built backwards from this.

Notes, pages, apps and the shell itself are documents that people and agents edit together, live, as in a shared doc: their words, styles, layout and components. An edit is data, never code, so it can break nothing but what it edits, and you can always get back to a screen that works. The editor is built and runs between tabs of one browser: try it, then open it again in a second tab.

Your files stay where they are, in the formats your tools read, and sync between your devices with history and merging, without converting a single file. Leave your.os and the folder is just a folder.

A terminal, files and anything else a machine does, from any of your devices, through any network, with the machine itself deciding who may.

Every laptop, server, browser and agent of yours is a key, and your account is the signed list of which keys are yours and what each may do. Add one from a device you trust; revoke one from any other.

Someone else's site, signed in, from any of your devices, without its script ever running where your keys are. There is one way to do it: a real browser in a box on one of your nodes, shown in a pane. None of it is built.

Who may do what, for every caller: your devices, your machines, the services and extensions on a node, an agent's MCP client, someone else's node. One rule covers them all: a caller is a key, it carries a chain of grants from your account, and the node holding what it asks for checks the call itself. None of it past call/chain and call/narrows is built.

An agent on your machine, Claude Code, Codex or anything else that speaks MCP, reaches your nodes through the node it runs beside, as a client of its own, with the grants you gave it and nothing more. It is off until you turn it on. None of it is built.

How your.os's own pages and apps are made, edited and shipped: this site and the shell are files on a machine, drawn by the same renderer that builds them, edited in the OS like any note, and released through the same gate as any code. For us first; a library for anyone's site, later. None of it is built: the site is still rendered by its own build.

Whatever forwards your traffic can't read it unless you granted it that, what is sealed today stays sealed, and a network that changes under you doesn't drop what you were doing.

A relay forwards sealed frames by key and reads nothing else. You can run your own or use ours, and leaving ours costs a setting.

The core is what you have to trust, so it is short enough to read: it holds keys, checks authority, seals and forwards, and everything else is a service.

A browser tab is your least trusted device: whatever its origin serves runs with its key. Later, a hostile page gets little, the network can stop being the page's source, and interception is noticed. None of it is built.

Code nobody vouches for (a browser full of other people's pages, an extension someone else wrote) runs on a node in a box: it sees only what it was given, reaches only what it was allowed, and every connection it makes is written down where you can read it. None of it is built.

What you have to trust, for what, and what stops each part from turning on you. Most of the limits are promises in other parts; this part maps them, and holds the ones about releases: how new code reaches your devices.

A promise is only as good as the test that would catch it broken, and this site can't claim more than the code does.