Cloud computers · 6 parts

What the system can do on computers in the cloud.

Containers (small computers) on Cloudflare’s servers run commands, scheduled jobs and AI coding agents, and keep running when your Mac is off. Android phones rented in a data centre and Mac virtual machines can be switched on when a job needs them.

Text me Every part

Automation on your devices

Part by part

What the system can do on cloud computers, part by part.

Each thing it can do on those devices is an action in the Directory, run through one address, and recorded in the Ledger.

Part 1 of 6

Cloud computers

Containers on Cloudflare’s servers that run whether or not your Mac is on, alongside the program on your Mac. One action reports whether both are running. Mac virtual machines can also be copied and started.

Examples

1The nightly job runs whether or not your laptop is open.
2A task that needs the Mac waits until the Mac is on; a task that does not need it runs straight away.
3Whether each computer is running is reported as a status you can read.

Text me about this

Part 2 of 6

Workspaces

A named folder on a cloud computer that keeps its files between runs: a copy of your website’s code, a Python report, a script that copies a web page at 6 a.m.

Examples

1Your website’s code is copied once and worked on for months.
2A report is produced every night from the same folder.
3Each workspace has its own row in the Directory and its own Ledger entries.

Text me about this

Part 3 of 6

Commands

Any command can be run on a cloud computer, inside a named workspace. The output, the errors and the time it took are written to the Ledger. It works like the Mac’s Terminal, without needing the Mac.

Examples

1A video cut, a report or an export is run from a text message at 2 a.m.
2A command that would keep your laptop busy for an hour runs on a cloud computer instead.
3The output, any errors and the time taken are kept.

Text me about this

Part 4 of 6

AI coding agents

An AI coding agent is started with a task. It returns the code it changed and a Ledger entry. The task counts as done only when its tests pass against the live system.

Examples

1“Fix the text-back timing” comes back as a code change you can read and a test that checks it.
2Several agents can work at once, each on its own copy of the code; their changes are combined by rule.
3A failure becomes a new task that names what allowed it.

Text me about this

Part 5 of 6

Android phones

Android phones rented in a data centre, with apps installed and phone numbers on them, switched on and off by an action. They are used for apps and messaging channels that only work on a real phone.

Examples

1WhatsApp, or another app that needs a real phone, runs without a phone on your desk.
2A phone is switched on for the job and switched off afterwards.
3Each phone has its own row, with its region and when its rental ends.

Text me about this

Part 6 of 6

Keys for one job

A key (a code that grants access) made for one job, with a limit and an expiry time, that stops working when the job is done. A program gets exactly the access it needs and no more.

Examples

1A refund key for one customer, up to $500, valid for ten minutes.
2A contractor’s door code, valid for one afternoon.
3Every use of the key is written to the Ledger.

Text me about this

The actions behind this page

Each of these is an action in the Directory, the table of everything the system can run.

146

actions in the Directory for your iPhone, your Mac, web browsers and cloud computers, counted on 27 September 2026. These are the Cloud computers actions.