Direct answer
Agent Studio sits between your application and the selected agent execution environment. Your application defines the task, access, and user experience. Agent Studio coordinates the run and returns status or results. The execution environment performs the permitted work against the assigned workspace and connected tools.
High-level layers
| Layer | Role |
|---|---|
| Your product | Collects the user request, applies business rules, and presents approvals, progress, and results. |
| Agent Studio | Coordinates agent work through a consistent product-facing control layer. |
| Execution environment | Runs the selected agent within the agreed workspace, tool, and permission boundaries. |
| Your systems and data | Provide only the repositories, files, services, or credentials approved for the use case. |
| Operations | Applies monitoring, support, retention, and incident responsibilities agreed for the deployment model. |
How work moves through your product
- 1Your product receives a user or system request.
- 2Your business rules define the task, available context, and permitted actions.
- 3Agent Studio coordinates the work in the selected execution environment.
- 4Your product receives progress, a request for input, completion, failure, or cancellation information.
- 5Your product reviews, presents, stores, or applies the result according to its own policy.
Security and control decisions
During implementation, your team defines data boundaries, deployment ownership, permitted tools, credential handling, approval points, retention, and operational access for the selected use case.
Implementation documentation
Your implementation includes documentation for the selected deployment model, interfaces, environment requirements, security responsibilities, and support process.