# Oracle introduced AI Agent Studio for building and managing Fusion application agents Oracle introduced AI Agent Studio for Fusion Applications on March 20, 2025, with tools to create, extend, deploy and manage enterprise agent teams. Canonical: https://rangoon.ai/insights/archive-oracle-fusion-ai-agent-studio-march-2025/ Author: Rangoon Editorial (https://rangoon.ai/insights/editorial/) Published: 2026-10-24 Updated: 2026-10-24 Event date: 2025-03-20 Tags: [Oracle](https://rangoon.ai/insights/tags/oracle/), [Enterprise AI](https://rangoon.ai/insights/tags/enterprise-ai/), [AI agents](https://rangoon.ai/insights/tags/ai-agents/), [workflow automation](https://rangoon.ai/insights/tags/workflow-automation/) Source note: Historical reporting: Oracle announced AI Agent Studio for Fusion Applications on March 20, 2025. Oracle described a studio for creating, extending, deploying and managing agents and agent teams in Fusion. Current Oracle documentation explains design-time tools, business-object access and optional human review, but is not launch-date proof. Oracle’s productivity claims do not prove a customer agent is authorized, correctly configured or appropriate for an HR, finance or supply-chain action. Image: Fusion agent team combines tools, topics and optional approval. Original Rangoon explanatory diagram: Source boundary: dated primary release reporting; original editorial analysis. No vendor interface, photograph, measurement result, or endorsement implied. ## Key takeaways - The event was an AI Agent Studio announcement within Fusion Applications. - Design, deployment and management are separate phases with separate controls. - Current documentation clarifies tools and review options without changing the March launch fact. ## Oracle announced AI Agent Studio on March 20, 2025 [source 1](https://www.oracle.com/ca-en/news/announcement/oracle-introduces-ai-agent-studio-2025-03-20/) Oracle’s March 20 announcement introduced AI Agent Studio for Fusion Applications as a platform for customers and partners to create, extend, deploy and manage AI agents and agent teams. The event places agent construction inside an existing enterprise-applications suite rather than describing a stand-alone general assistant. That context matters because an agent can interact with HR, finance, supply-chain or other application objects. The announcement establishes the product direction and date. It does not prove a specific organization created an agent, connected it to records or allowed it to carry out a business operation. ## Oracle framed the studio as a design and management environment for agent teams [source 1](https://www.oracle.com/ca-en/news/announcement/oracle-introduces-ai-agent-studio-2025-03-20/) [source 2](https://docs.oracle.com/en/cloud/saas/fusion-ai/26b/aiaas/get-started.html) The launch distinguishes creation from extension, deployment and management. Those words map to a lifecycle: teams can start from a supplied capability, adjust it for a business need, publish it into an application and later operate it. Current Oracle documentation describes templates, tools, topics and agent teams as design-time components. That is useful implementation context, but it cannot retroactively establish every detailed feature as available on March 20. The release should be read as an announcement for Fusion customers and partners, while current documentation describes a later product surface that may vary by release and subscription. ## Current documentation identifies business objects, connectors and document tools as different agent inputs [source 1](https://www.oracle.com/ca-en/news/announcement/oracle-introduces-ai-agent-studio-2025-03-20/) [source 2](https://docs.oracle.com/en/cloud/saas/fusion-ai/26b/aiaas/get-started.html) Oracle’s current guide describes tools for business objects, connectors, documents, email and external REST services, along with topics that shape an agent’s scope. These inputs are not interchangeable. A business-object tool can retrieve or alter application records; a document tool supports information retrieval; an external connection adds another system boundary. The documentation also says access follows Fusion role and security controls. That explains why an agent studio needs more than a natural-language instruction. It does not establish the configuration of any customer tenant or the correctness of a generated workflow. Those would need deployment-specific evidence outside the product material. ## The guide describes optional human review as a workflow decision rather than a launch outcome [source 1](https://www.oracle.com/ca-en/news/announcement/oracle-introduces-ai-agent-studio-2025-03-20/) [source 2](https://docs.oracle.com/en/cloud/saas/fusion-ai/26b/aiaas/get-started.html) Oracle’s guide says a human-in-the-loop approval can be added before actions such as sending email or updating a record. This is a precise product-control detail: it describes an available design choice, not proof that every agent action receives review. The March announcement’s productivity language should therefore remain separate from a customer’s approval rules. A team evaluating the studio needs to know which tools have write capability, which roles may invoke the agent, how an approval is configured and what logs remain after a run. The launch event makes AI Agent Studio newsworthy; the adoption decision requires the later configuration evidence the announcement does not contain. It should also record whether an approval rejects, modifies or merely observes a proposed action. ## Sources 1. [Oracle: AI Agent Studio announcement](https://www.oracle.com/ca-en/news/announcement/oracle-introduces-ai-agent-studio-2025-03-20/) 2. [Oracle: Get Started with AI Agent Studio](https://docs.oracle.com/en/cloud/saas/fusion-ai/26b/aiaas/get-started.html) ## Related reading - [UiPath launched an agentic-automation platform spanning agents, robots and people](https://rangoon.ai/insights/archive-uipath-agentic-automation-platform-april-2025/) - [ServiceNow’s Yokohama release put preconfigured AI-agent teams into business workflows](https://rangoon.ai/insights/archive-servicenow-yokohama-ai-agents-march-2025/) - [Salesforce announced Agentforce 2.0 with a staged availability plan for skills, Slack and reasoning](https://rangoon.ai/insights/archive-salesforce-agentforce-2-december-2024/) ## More information - [Documentation index](https://rangoon.ai/llms.txt) - [AI access and policies](https://rangoon.ai/ai/) - [Source repository](https://github.com/hypler-dev/rangoon)