
Space combines model usage with a cloud...
When a coding agent needs to stay on, sessions, files, and previews can remain in the cloud workspace and continue from another device. One credit balance covers the models. Pay-as-you-go channels do not require buying a specific plan first and charge what the call actually uses. A plan can cover the models you use most, then fall back to pay-as-you-go. The developer API can carry that balance to other agent products. Some official group subscriptions are still marked as opening soon, and the dedicated cloud Mac is only described as a first batch. It fits teams already using several coding agents who want credits and cloud sessions in one place.
Agent.Space combines model usage with a cloud coding workspace. Codex, Claude Code, and other coding agents can keep running there, with sessions, files, previews, and team context stored in the cloud. A developer API can carry credits and plans into other agent products. Usage shares one credit balance: pay-as-you-go channels charge the credits actually consumed, plans cover the models you use most, and calls fall back to pay-as-you-go when the allowance runs out. A dedicated cloud Mac in California, assigned to that user, is listed as open for a first batch.
Difficulty: Intermediate
Always-on cloud workspace
Codex, Claude Code, and other agents keep running in the cloud, with sessions, files, previews, and team context kept together.
Credits and model plans
One credit balance covers the models. Pay-as-you-go charges actual use, and a plan falls back to pay-as-you-go when its allowance runs out.
Developer API passthrough
Plans and credits can be used in other agent products through the developer API, not only inside this workspace.
Dedicated cloud computer
The site offers a cloud Mac in California for that user alone, and says the first batch is open.
Continue coding in the cloud
A developer leaves a Codex or Claude Code session in the cloud so files and previews remain after the local machine is closed.
Share one model balance
One credit balance serves several models, with a plan for the models used most and pay-as-you-go for the rest.
Carry credits to another tool
Use the developer API to take existing credits and plans into another agent product.
The page splits the product in two. Model plans share one credit balance: pay-as-you-go charges actual use, a plan can cover the models you use most, and calls fall back when the allowance runs out. The cloud workspace keeps coding agents running, with sessions, files, and previews in the cloud. You can use them together, or pass the balance to other products through the developer API.
The page describes a dedicated Mac in California for that user alone, and marks the first batch as open. It is listed separately from the cloud workspace: the workspace keeps agents running, and this Mac is its own machine. The page does not explain how later batches queue, and it does not say every account already has one.
Yes, through pay-as-you-go. The page says those channels need no purchase first and charge credits for the usage actually consumed. Credits themselves come from a top-up or from a credit subscription that refills on a schedule. A model plan's allowance is used first; when it runs out, or for models outside the plan, calls switch back to pay-as-you-go.
Real reviews and feedback from users