Oracle puts Fusion setup know-how in a public Git repo for AI agents

Oracle on Monday introduced the Oracle Fusion Setup and Configuration Registry (FSCR), a public Git repository that lets AI agents plan, run and test setup work directly inside Fusion Cloud Applications.

A Git repository of executable setup skills

Oracle announced FSCR at its Oracle AI World event in Las Vegas. According to the company, it builds and continuously maintains the registry, which holds its product expertise and best practices as reusable AI skills. The skills cover configuration options, dependencies, sequencing, execution, testing and validation.

The idea is that agents no longer work from static guides. Oracle says AI assistants and coding agents, including those from OpenAI, can take business requirements, process documents, policies and existing configurations and turn them into implementation runbooks. The agents then make the changes in Fusion Applications and test the results automatically. Human experts review the finished configuration, can ask for changes, and approve it for deployment.

Oracle is explicit that the registry is meant to be shared. Systems integrators can build their own methodologies, accelerators and industry solutions on top of it. Partners including Accenture, Apex IT, Deloitte, Grant Thornton and PwC were quoted in the release.

Chris Leone, Oracle’s executive vice president of Applications Development, framed it this way:

“The Oracle Fusion Setup and Configuration Registry is like having an expert Oracle product manager guiding teams through the entire setup and configuration process.”

What the release leaves unanswered

The announcement does not say what FSCR costs, whether any Fusion license tier is required, or which Fusion modules the skills cover today. It also gives no licensing terms for the repository, although Oracle and several partners call it open or open-source. No figures on time saved are given, so the claim that it speeds implementations rests on Oracle’s own description and has not been independently verified.

Nor does the release explain how agents get access to a customer’s Fusion environment, or what controls apply to changes agents make. The only safeguard it describes is the expert review and approval step before deployment. Customers weighing the registry will want those details, since setup changes touch finance, HR and supply chain records.

For readers who run Fusion projects, the practical change is the source of truth. Until now, configuration knowledge lived in documentation and in consultants’ heads, which Leone says can go stale as new features arrive. A registry that is versioned in Git and maintained by Oracle alongside the product could let teams track what changed between releases the way developers track code.

A partner push that now has a product behind it

The registry follows Oracle’s partner announcement from last week. As we reported on October 23, Oracle committed $1 billion over four years to its partner ecosystem, covering training, technical help, migration funding and joint marketing. That program named Accenture and PwC among its Fusion Applications partners, the same firms that now endorse FSCR.

Read together, the two moves point at the same bottleneck. Implementation work is largely done by integrators, and Oracle’s partner network has more than 20,000 members, according to ITPro. Making the repetitive layer of that work machine-executable changes what those firms sell, and Oracle is also paying them to retool. Several partner quotes say as much, describing a shift from routine configuration toward industry-specific services.

It also sits inside a wider race for partner loyalty. Cloud Wars reported in April that Google Cloud unveiled a $750 million ecosystem investment, so Oracle’s $1 billion figure is aimed at the same group of firms. Oracle’s financial position adds pressure to show returns: its fiscal 2026 results, filed in June, showed $638 billion in remaining performance obligations and negative free cash flow of $23.7 billion, which it attributed to infrastructure spending. Applications that sell faster and deploy faster help turn that backlog into revenue.

The release ties FSCR to Oracle’s Fusion Agentic Applications and its AI Agent Studio, which suggests the registry is meant to be the on-ramp to those products. Oracle does not say when customers can start using the repository, so the pace of adoption will depend on how complete the published skills turn out to be.