You Already Have a Computer in the Cloud

On August 11, xAI's Grok Bot entered beta. One sentence on the product page, tucked into the feature list, is easy to miss: every bot gets "its own persistent cloud computer, with a real browser, file system, and terminal," and when you close the app, it keeps working. That sentence could have been a bare spec. Put next to two other companies, it becomes something else. Manus has a help-center article explaining what a Cloud Computer is: one persistent virtual machine per user, with no temporary sandbox for each session. It keeps running after you close the browser, what you installed stays, files stay, and processes can be resident. The first line of the Cursor Cloud Agents page is "cloud agents control their own computers." You can work out a plan locally, hand it to the cloud to run while you're offline, or start one straight from your phone. On August 14 SpaceX completed its acquisition of Cursor, so this will grow into Grok's system next. The three serve different customers. Manus targets general tasks for ordinary users, Cursor targets developers, and Grok Bot sits under a premium subscription of $200 to $300 a month. Their messaging differs too. None of them leads with "we give you a computer in the cloud." It sits in the help center, or on the third line of a feature list, like an implementation detail. But from entirely different starting points the three arrived at the same structure: for every user, a machine in the cloud that belongs to them for the long term. Why they converged Work backward and there is hardly another option. A truly person-centered agent has to do all of this: stay online all the time, push long tasks forward in the background for hours or days, stay connected in state when you attach from another device, keep working while you sleep, and run in an environment where anything can be installed and changed freely, with breakage that can't spread to your own machine. A personal device can do none of these. A phone shuts down or runs out of battery, a laptop sleeps when the lid closes, and the one issued by your company is managed by MDM, with installs and removals out of your hands. The key isn't compute. On-device models have not been running slowly in recent years. What can't be crossed is the availability model. A personal device's default state is "it is there when you are," and an agent needs "it is there when you aren't." There is no middle state between the two, and no amount of local compute fills the gap.