What the system can doCloud computers
One family of actions
Cloud computers
Computers on Cloudflare’s servers, Mac virtual machines and Android phones in a data centre, for work that keeps running when your own computers are off.
A virtual machine is a computer that exists as software on a larger one. These actions create them, run work on them and remove them.
Live, read from this site just now.
The groups in this family, counted just now: — actions
This family among all — actions in the Directory, one square each
Each action is one row in the Directory, sorted into this family by the start of its name.
What it can do
What the actions in this family do, group by group.
Each card is a group of actions that do similar work. The number on each card is how many actions are in that group right now.
Switch to “For your developer” to see the real name of every action.
The real name of every action, read from the Directory just now. Names that contain a supplier’s name are left out of the lists, and still counted.
Workspaces
—Create a computer on Cloudflare’s servers, with a code repository (a project’s files and their history) copied in if you like, run commands in it, keep a command window open between commands, and remove it when done. Its record is kept.
Long jobs
—Start a job that keeps running after the request that started it ends, check its progress, read its output, or cancel it.
Containers
—Start a container (a small, separate computer on Cloudflare’s servers), run a command in it, and read, write or delete its files.
Mac virtual machines
—Download, copy, start, stop and delete macOS virtual machines, to run Mac-only work apart from your own Mac.
Phones in a data centre
—Switch rented Android phones in a data centre on and off and read their status, for apps that only run on a phone.
Health
—Check that the cloud computers, the connection to your Mac and running jobs are all up.
Uses
What a business uses these actions for.
Examples of the work these actions do. They describe uses, not results.
Run a long job overnight without leaving a laptop open.
Use an app that only runs on a phone, on a phone in a data centre.
How it is run
How any of these actions is run.
The same way as every other action in the Directory: one request, the same permissions, one record.
You don’t have to pick an action yourself. You text what you want; the AI assistant picks the action and runs it within the permissions you set. The result comes back to you, and the request, the result and who asked are written to the Ledger, the record of everything the system has done.
Every action is one row in the Directory, and each row can be run — ways: a text, a link, a spreadsheet cell, an iPhone Shortcut, a command, or an AI model’s request. Every way goes through dispatch: one web address that looks the action up, checks the permissions, runs it on the right computer, sends back the result and writes a Ledger entry. The same action answers every way, under the same limits.
Dispatch takes an HTTP POST (a standard web request) of {"key": "<action name>", "args": {…}}. The same key works over the API (the web address your software calls), MCP (Model Context Protocol, the standard way AI apps connect to outside tools), the command line (CLI), a webhook (an address another program posts to), a spreadsheet cell or a Shortcut. A token (a key or a link) can be limited to exactly the actions you allow; every call, and every refusal, is a Ledger entry.
// One action from this family, as dispatch receives it
{ "key": "…", "args": { … } }Ask for this.
The text below opens ready to send. Add a line about your business, and I’ll reply with what this family of actions would do for it.
Every family
Everything else the system can do.
Every family of actions, with how many actions it has right now.