Understand your App Cloud
Your App Cloud. Build apps. Run agents. An app gives people an experience: a workspace, a website, a conversation, or a place to create. An agent works toward a goal using the context and actions you give it. The cloud provides the supporting capabilities and a home for the result.
What your app is made of
Section titled “What your app is made of”| Part | Its job | Example |
|---|---|---|
| Experience | Give people a way to interact | A question box and a list of saved answers |
| Models | Interpret or generate information | Language for answers; vision for documents; media for images and video; voice for conversation |
| Context | Supply relevant information | Approved reference files and the user’s question |
| Data and files | Keep information beyond a request | Saved projects, documents, and results |
| Access and services | Support everyday use | Sign-in, permissions, email, and secure connections |
Choose the pieces that serve the purpose. A public portfolio may need no agent. A research workspace may need language, files, saved results, and a review step.
Building and running are different
Section titled “Building and running are different”The building assistant helps create and change the app in Studio. An agent inside the finished app helps its users with a task. Describe its inputs, permitted actions, stopping conditions, and when someone should review its work. Adding a chat screen alone does not define those behaviors.
Draft and published
Section titled “Draft and published”Preview the working version before publishing. A published link makes the app reachable; its access rules determine who can see information or change it. Treat app changes, record changes, and model usage as separate things to review.