Machines

What you can do↑ Why · Alex reaches the laptop at home from a café Alex's shell on the home laptop, from a café, carrying on when the wifi drops.

Open a shell on a node from a browser, and reattach after a drop

A session dies with its pipe; the shell must not.

List, read and write files on a node

Its desktop↑ Why · Alex reaches the laptop at home from a café Alex uses the home laptop's desktop from a café while the laptop sits locked on the desk.

A node's desktop in a pane: see it and use it.

See and use a node's desktop from a browser

A desktop of its own, while the machine stays locked

Nothing remote shows on the machine's screen, and locking or unlocking that screen doesn't touch the remote desktop. It needs no root, and it works with nobody logged in.

The screen at the machine, only while it is unlocked

A locked screen is never shown or unlocked from afar: whoever walked away from it decided.

The desktop is the pane's size

A lost frame never holds up the next

Many watch, one types

It mends itself

The desktop is a right of its own

A grant to the shell or files doesn't open the screen.

Every call is checked

The machine with the data checks every call itself, against grants you signed. No server is asked, so it works offline. Who may call, and how a person is asked, is Access; an agent's way in is MCP.

Staying up to date↑ Why · Alex reaches the laptop at home from a café The laptop at home takes every fix without Alex going back to it, and never mid-session.

A machine you set up once keeps itself current: nothing to type, nothing interrupted, and nothing installed that we didn't sign.

A node updates itself

It looks for a release when it starts, every fifteen minutes and as soon as its relay says one is out (wire/release-hint), downloads it and switches to it, with nothing typed on the machine.

Only a release we signed is installed

A release is a manifest of its version and each build's SHA-256, signed with the release key, Ed25519 and ML-DSA both (D-2). The node carries the public key; the host serving the downloads can't make it run anything.

Never an older version

A node restarts into an update only when nobody is using it

It downloads and checks at once, then waits until no session has carried anything for a few minutes and no file is open, or a day has passed.

A release that doesn't come up is rolled back, and never tried again

The new build has a minute to attach to the relay, start its services and load the account's log; if it doesn't, the machine goes back to the build it had, and skips that release from then on, still taking a later one.

Updating a service restarts only that service

Sessions stay up; a call in flight to it gets gone.

Services outlive a restart of the node

The new node takes over the services the old one started, through their sockets, so a shell survives an update of the core.

An extension updates on its own, signed by its publisher

Never by our key, and never along with the node.

#What you can do↑ Why · Alex reaches the laptop at home from a café Alex's shell on the home laptop, from a café, carrying on when the wifi drops.

#Open a shell on a node from a browser, and reattach after a dropproof

#List, read and write files on a nodeproof

#Its desktop↑ Why · Alex reaches the laptop at home from a café Alex uses the home laptop's desktop from a café while the laptop sits locked on the desk.

#See and use a node's desktop from a browserproof

#A desktop of its own, while the machine stays lockedproof

#The screen at the machine, only while it is unlockedproof

#The desktop is the pane's sizeproof

#A lost frame never holds up the nextproof

#Many watch, one typesproof

#It mends itselfproof

#The desktop is a right of its ownproof

#Every call is checked

#Staying up to date↑ Why · Alex reaches the laptop at home from a café The laptop at home takes every fix without Alex going back to it, and never mid-session.

#A node updates itselfproof

#Only a release we signed is installedproof

#Never an older versionproof

#A node restarts into an update only when nobody is using itproof

#A release that doesn't come up is rolled back, and never tried againproof

#Updating a service restarts only that serviceproof

#Services outlive a restart of the nodeproof

#An extension updates on its own, signed by its publisherproof