Studio is where the tool gets built and validated. Cloud is where delivery happens, with hosted runtime, configuration, and access handled in one place, then used mainly through oo-cli by agents.
In Studio, generate, combine, and extend tools around your business needs. After publishing to Cloud, runtime and access control are managed in one place.
In Studio, you can write code to create new function tools and combine existing ones. After publishing to Cloud, those capabilities become new tools that keep running reliably.
No matter which agent you use, once it is connected through oo-cli it follows the same account and permission system. Your tool capabilities move with you instead of being tied to one agent.
Publish the tools you generated and combined in Studio to Cloud. After launch, Cloud handles runtime and access management so you do not have to maintain them separately.
Users do not need to care about deployment details or change habits. With oo-cli connected, they can keep using the same toolset across different agents.
Cloud Task runs your published tools on demand. Start without buying servers or reserving capacity, then scale based on actual runtime usage.
Put the tool online, check that it runs reliably, and make sure agents can find and run it through oo-cli.
A good fit for first tools, lightweight jobs, and everyday trials.
You do not need to buy servers or reserve capacity in advance. Billing is based on actual run time, so you can grow when demand grows.
Scale only when usage grows.
Cloud handles post-launch management, while your team keeps the same oo-cli workflow.
