Studio is where the tool gets built and validated. Cloud is where it gets delivered, with hosted runtime, configuration, and access handled in one place, then mainly flowing back into oo-cli for agents to use.
Once the tool works locally, what slows launch is usually not the logic itself but the layer around it: hosted runtime, access control, secrets, and delivery. Cloud exists to compress that layer.
Cloud takes over delivery, configuration, access, and runtime relationships so you do not need a separate publishing backend wrapped around the same tool.
Users primarily keep consuming the tool through oo-cli. When you need API, MCP, or automation surfaces, you can add them from the same hosted layer while the implementation stays on the server.
Once the tool is validated, Cloud takes over delivery and keeps hosted runtime, runtime settings, secrets, and access control in one place. The default primary delivery path still flows back into oo-cli.
Once the tool is delivered, it still mainly flows back into oo-cli for agents instead of being rebuilt behind another service layer.
Keep runtime settings, secrets, and environment differences in one console.
Manage permissions, runtime status, and usage relationships without splitting them across tools.
Keep delivery, runtime settings, secrets, and access control in one backend.
For the user, there is no need to understand your implementation or learn a new workflow. Once delivered, they still search, inspect, and use it through oo-cli. APIs, MCP, and automation remain optional extension surfaces.
Show a delivered tool being searched, inspected, and called in Codex.
Free users get 200 Cloud Task minutes refreshed every month. Use them to deliver the tool through Cloud first, then top up or upgrade when the quota is not enough.
Use the monthly refreshed quota to deliver the tool and confirm it stays searchable and callable in oo-cli.
A good fit for first delivery, lightweight jobs, and everyday trial use.
You do not need to buy servers or reserve fixed capacity up front. Pay for actual call time only after the included quota runs out, and expand only when demand grows.
Start using it first, then decide the scale.
Use Cloud to handle delivery, hosted runtime, configuration, secrets, and access control, then keep the tool flowing mainly back into oo-cli.