Orrery Cloud and your machines

Orrery Cloud lists your machines and their sessions on every screen: the web, the ADE, the phone and orrery machines. A change on one shows on the others within about a second.

#Hosts, machines, sessions

A host usually has one machine. Add a second machine only to keep separate state on the same host, for example a development home beside your daily one; it is named <host> (dev). For different providers, rules or settings, use a profile instead: it needs no second node.

The Machines page groups machines by host. Power controls name the machines they stop.

#Join once

orrery node join https://<relay>        # device code, then approve in the browser

A computer is joined once. Joining again with a valid enrolment changes nothing:

already joined as VECTORGP66

--json prints { "already": true, "machine_id": …, "machine_name": … } and exits 0, so a script can run the command every time.

Joining also installs the autostart (the same as orrery node up --install), so the machine comes back after a restart with its old sessions. orrery node down --uninstall removes it.

Joining sends this machine's configuration to Cloud, keys included (secrets sealed).

#Take over

If the same computer and home join with a new key, for example after the key file was lost, Cloud offers to take over the old machine instead of adding a second. Tick Take over on the approve page. The old key stops working, and the machine keeps its name and sessions.

#key_in_use

A key can run on one computer at a time. If it is copied to another computer while the first is online, the second is refused:

this key is in use on another computer; run `orrery node join --force` here to make it a new machine

Run the command it names on the second computer.

#Add a machine on an instance

On the Machines page, Add a machine on an instance's host creates another machine on it, with its own home. Remove deletes it (the default machine stays). The machines share the instance's limits; set an optional cap per machine from its page.

#Configuration syncs by itself

There is no sync button and no "use Cloud's". A change to a joined machine's configuration, by hand in config.toml or from a flow, goes to Cloud within seconds. A change made in Cloud reaches the machines it covers and applies to the next session, with no restart. The last write wins.

If the machine is offline, its changes wait and go out when it reconnects.

Each machine page and the Extensions page show a Config history: who changed a key, where, when, and the previous value (secrets are masked). Restore writes that previous value back, which is itself a new history row.

#Continue a session whose machine is off

A session on an offline machine is still readable. Open it and choose:

• Start & continue (an instance that is off): Cloud powers it on, waits for it to come online, and attaches.
• Move to…: any online machine of yours, instances and computers alike. It carries the uncommitted work, as in orrery handoff <session> --to <machine>.
• Start Orrery on <machine> (your own computer that is off): Cloud shows the command to run there. Cloud cannot wake it.

#In the ADE

See Agent mode.