What is a cloud agent? An always-on AI agent with its own computer, explained
A cloud agent is an AI agent that runs on a computer of its own in the cloud: always on, with a browser, files, logins and memory that persist. Where the term came from, the two shapes that share it, and the three ways people get one.
A cloud agent is an AI agent that runs on a computer of its own in the cloud, rather than inside a chat window or on your laptop. The computer is always on, so the agent keeps working while you sleep and answers at 3 a.m. It has a real browser, a terminal and a filesystem, so it can do things rather than describe them. And its state persists: the sites it is signed into, the tools it installed, the notes it kept and the memory it built are still there tomorrow. You talk to it from your phone, usually through a chat app it lives in. The term arrived in 2026 as practitioners moved their agents off their own machines and needed a word for what they had moved them to.
Where the phrase came from
Nobody coined it in a press release. It surfaced in the way engineers talked about their setups through the summer of 2026: “day one of moving to cloud agents,” a developer wrote after leaving a laptop that maxed out at five parallel tasks; another described himself as “extremely cloud agent-pilled”; a third made the team argument, that “another benefit to cloud agents is you just set it up once and you can add other ppl,” instead of configuring everyone’s laptop and sharing every key by hand. The word describes the machine as much as the software. An “AI agent” is a program that plans and uses tools. A cloud agent is that program plus a computer that is always there.
Two shapes wear the same name
The phrase is used for two quite different things, and most confusion about it comes from mixing them.
The disposable runner. Coding-agent products spin up a fresh machine per task: clone the repository, install dependencies, do the job, throw the machine away. Parallelism is the point, and the price is that every task starts from zero: the developer above spent “a few hours” writing setup scripts, one per provider, so each fresh machine could reach his logs and tools. Nothing accumulates.
The persistent home. One machine that belongs to one agent and stays. Logins stay signed in, tools stay installed, memory grows, schedules run. This is the shape people mean when they talk about an agent “living” somewhere. The open-source agents OpenClaw and Hermes are built for it; so are the closed products that arrived in 2026, from Grok Bot’s per-account computer to the “AI teammates” services. The two shapes suit different jobs, and the first decision about any cloud agent is which one you are buying.
What makes it a cloud agent and not a chatbot
- Its own computer. A browser it can drive, a shell it can run commands in, a disk it can write to. A chat window has none of these; a chatbot with tools borrows them from a sandbox that vanishes when the conversation ends.
- Always on. A scheduled job at 06:00, a periodic check every half hour, a message answered while your laptop is closed. The machine does not sleep, roam between networks, or go into a bag.
- Persistent state. Signed-in sessions in a browser profile, installed packages, keys, notes, and a memory that consolidates over weeks. This is the property that separates an agent from a very good autocomplete.
- Reachable from wherever you are. Usually through a messaging app (Telegram, WhatsApp, Slack) or a vendor’s own app, so the interface is your phone and the work happens elsewhere.
Why the computer is the part that matters is its own question; the short version is that everything on that list except the first is impossible without one.
What it is not
It is not a chat product like ChatGPT or Claude in the browser, however capable: those forget the machine between turns. It is not a coding assistant running in your terminal (Claude Code, Codex CLI): those are agents, but they live on your laptop and stop when it does. It is not workflow automation (Zapier, n8n): those run steps you designed, not an agent deciding. And it is not necessarily a fleet. The commonest cloud agent is one agent on one small machine.
The three ways people get one
Rent a server and install an open-source agent. A small VPS for a few dollars a month, plus OpenClaw or Hermes, plus the model provider of your choice. You own everything and administer everything: the operating system, the updates, the security posture, the backups.
Buy a vendor’s closed product. Grok Bot gives every account one always-on computer in xAI’s cloud; Squad sells named teammates on a dedicated computer that runs on the ChatGPT or Claude plan you already pay for; Nous Research’s Hermes Cloud is in preview. Zero setup, and the vendor decides the model, the apps, and what persists. That last point is worth reading before you sign: Grok Bot’s own docs say files in /workspace, browser state and supported sign-ins “are designed to survive normal computer updates,” while “manually installed packages” are replaceable and may be discarded. A computer where only one folder survives an update is a narrower promise than the word “computer” implies.
Managed hosting of an open agent. The middle path: the agent is the open-source one, the machine is yours alone, and a host does the operations. What you keep is the portability: the agent’s files, memory and configuration are plain data you can take elsewhere. The comparison, including the Mac mini many people buy instead, lays the three out side by side.
Questions to ask any cloud agent
- What survives an update or a restart: the whole machine, or one folder?
- Who can see the machine, and what do they promise in writing about when they look?
- Which model does it run, and whose plan pays for it?
- Is the agent one process on a shared computer, or does it have a machine of its own?
- Can you leave with your agent, or only with an export?
The answers separate a computer for an agent from a subscription that resembles one. Both can be the right purchase. Knowing which you are holding is the point of having a name for it.