Cloud

What a cloud machine is

A cloud machine is Mori running on a Linux machine of her own, for one thread. The thread's agent loop runs there instead of on your computer, with the thread's repo in its work folder, so the work carries on when you close the lid.

Cloud machines come with every paid plan. Free has none. They are for work that must keep going: a long task over days, a build that takes hours, a job you start before you leave.

Moving a thread

Three commands move a thread:

• Run on Cloud starts a new thread on a cloud machine.
• Continue on Cloud moves a thread between turns.
• Return to This Mac brings it back to your computer.

Cloud threads are switched on in Settings > Connections. A move always happens between turns, never in the middle of one.

What travels and what does not

When a thread moves out, your computer takes a snapshot of the thread's repo: the current commit, what is staged and what is changed in the working tree. Never what git ignores, never a secrets file, and the move is refused if a key you registered appears anywhere in it. The snapshot is uploaded as a checkpoint, and the machine restores it on its first boot.

The conversation itself stays with your own apps, and when the thread comes back, the work comes back with it, filtered by your own ignore rules.

One place at a time

A thread has one holder at a time, kept by a lease. Your computer takes the lease before a move, hands it to the machine, and the machine renews it while it works. The moment a renewal says the lease was lost, the machine stops taking turns. So a thread is never worked on in two places at once, and taking it back is a clean hand over, not a race.

Long tasks keep going

On your computer, closing Mori or the lid pauses a long task. On a cloud machine it keeps going while your computer sleeps: the machine starts its own next turns, within a charter your computer signed. The charter names the task's milestones, its budget and what it has spent, its deadline, its pace and quiet hours in your own time zone, and how many turns a day the machine may start.

The machine cannot write itself a charter, a bigger budget or a later end, even if something on the machine tried: only your computer's signature counts. See Long tasks.

Machines and hours

• Standard: 2 vCPU, 4 GiB of memory and 10 GiB of disk.
• Large: 4 vCPU, 8 GiB of memory and 10 GiB of disk, counted as two hours for each hour it runs.

Cloud hours a month: Plus 40, Pro 120, Studio 300, Max 600. Machines at once: Plus 1, Pro 2, Studio 4, Max 8. Cloud storage for checkpoints: Plus 25 GB, Pro 75 GB, Studio 150 GB, Max 300 GB.

The account portal shows cloud hours and storage used, live, and the long task card shows the machine's cost and the hours left.

Idle machines stop themselves

A machine is only billed while it runs, so Mori stops her own machine a few minutes after its thread goes idle, and a machine whose heartbeat goes quiet is stopped by the service. A stopped machine keeps its work folder, and waking it carries on where it left off. After two days stopped it is archived, which costs nothing, and a machine nobody has used for 30 days is deleted.

Security

Every message between your computer and a machine is signed with the thread's own key. The cloud service your computer talks to may only be studiomori.ai over https (or a test service on your own computer); any other address is refused, because your sign in travels to it. Secrets never travel in a snapshot. See Security.