Cloud and subscriptions

Agentic Cloud Computer is free to use. There is no paid tier, no checkout and no billing system behind the Workspace: it does not take payment details and cannot charge you. The cloud your agents run on comes with the platform.

• AI: your Claude or ChatGPT subscription, billed by Anthropic or OpenAI as it always was.
• Cloud: nothing. The agents’ machines, your sites and your files run on the cloud at no charge to you.
• Anything else you connect, such as a GitHub account: on that provider’s own terms.

Three kinds of thing run on the cloud for your workplace. There is nothing to connect first.

• One machine per agent. It keeps its files between turns, sleeps when idle and wakes in seconds when there is work. See The machine and Sleep and wake.
• The sites your agents deploy, each on its own small machine. See Production sites.
• Your files: the ones sent in chats, put on notes, proposals and knowledge pages, and everything in Drive. See Where files live.

Repositories live on the platform’s own git storage, unless you use a host of your own; see Where code lives and the Privacy Policy for the full split.

A workplace holds up to twenty agents and ten live sites, counted across everyone in it and every room. A site counts while it is live or being set up. At the limit, delete an agent you no longer need before you create the next one, or take a site down to put up another.

Every member can read the workplace’s Cloud card, on Workplace settings: how many of its agents and sites are in use. There is no bill, so there is no spending screen behind it.

A subscription you have signed in is called a seat: a Claude Pro or Max plan, which runs agents on Claude Code, or a ChatGPT Plus or Pro plan, which runs them on Codex (see Sign in a subscription). The agents run the official Claude Code and Codex CLIs on their own machines; the platform gives them the machines, and the plan itself stays between you and Anthropic or OpenAI. It is yours alone. It runs only your own agents, and no teammate, admin included, can see its credential or its usage. Several of your agents share one seat, and you can use the same seat in several of your workplaces at once.

Your subscriptions appear as a strip on Home, one tile per subscription with its usage, and Add sub opens Your subscriptions. There you sign in another, or bring in one you use elsewhere with Use here. With more than one seat of a provider, Make primary here puts one first; when it is paused, your agents fall back to the next ready seat of the same provider. Unassign from this workplace keeps a seat working in your other workplaces, while Remove subscription everywhere signs it out of all of them.

A subscription has windows: an amount for a short period and an amount for the week. A Claude seat shows 5 hours, 7 days and a weekly window per model. Each shows the percentage used, when it resets, and a mark where an even pace would be by now. A high percentage late in the window is fine; a high one early means the agents will hit the limit before it resets, and the pace line forecasts when. An agent that reaches the limit pauses at Session limit and picks up again on its own once the window resets. When Claude pauses a subscription, usually a billing matter on their side, the seat’s screen says so and offers Open Claude billing.

Every agent’s machine has a size: how many processor cores, whether they are shared or dedicated, and how much memory. The standard for a new agent is two dedicated cores and 4 GB of memory, which is a good size for almost all work. The ladder runs from one shared core with 2 GB up to eight dedicated cores with 16 GB.

• Shared cores: one, two or four cores with 2, 4 or 8 GB. A shared core is throttled hard under sustained load, and the same job can take many times longer there.
• Dedicated cores: one, two, four or eight cores with 2, 4, 8 or 16 GB. The standard is in this list.

Memory is a wall, not a slope. There is no swap, so work that outgrows the memory is stopped rather than slowed, and the fix is one step up the ladder.

An agent’s owner, whatever their role, resizes that one agent from its own screen, in its Machine row. A resize is refused while the agent is mid-turn. An awake machine restarts and stops for about a minute; an asleep one wakes up on the new size. Files are kept either way.