Fusion Claw Is Arriving in 26D. Here Is What We Are Doing Before "Turning it On".

Fusion Claw Is Arriving in 26D. Here Is Why We Are Not Turning It On Just Yet.

Visible is not the same as approved. The governance conversation to have before your first Claw run.

Oracle associated Fusion Claw with 26D. Customers in the early access cohort should see it first, and everyone else gets it with their cohort's release.

One practical detail: Oracle told us some of the capability did not make the initial general availability build, so an environment on 26D may still need a weekly CWB update. Oracle offered to look at our environment with us and confirm whether the required build is present. I would recommend asking for the same.

The model question

Fusion Claw requires frontier models. Oracle told us plainly that GPT-OSS, the model it hosts at a zero multiplier, is not capable enough for it. And if you use it, it will call a frontier model hosted by OpenAI.

If your organization approved Fusion AI on the basis of Oracle-hosted models, Fusion Claw is a new conversation, not a footnote to the old one.

There was a useful nuance here that I suspect many people have not considered. Even GPT-OSS runs outside your Fusion tenancy. Oracle hosts it in OCI data centers in Chicago and Frankfurt, and Fusion calls out to it. So the real question was never inside the tenancy versus outside it. It is Oracle-operated versus third-party operated.

For many organizations, there is precedent. Plenty of us already use frontier models hosted by third parties through other tools. Precedent makes the review easier. It does not make it unnecessary.

Oracle has documentation describing how data flows to LLMs and told us it has used it to help other customers, including defense and government customers, work through the same concerns. Get it into your review early.

What you can point to in that review

The good news is that Oracle has given security and architecture teams quite a lot to work with. Based on what was described to us:

·        User-token enforcement. All data access and actions use the invoking user's token and functional rights.

·        Layered roles. Users need the role for each agent and for the agentic app. App access does not grant missing agent access.

·        Capability scoping. Authors decide which agents and capabilities a Claw can use.

·        No credential custody. The Claw plans and orchestrates. Agents execute.

·        Private runtime. Generated code runs in a private container hosted by Oracle in OCI.

·        Configurable retention. Session state is kept for up to 90 days, and you can set that period.

·        Tenant-specific learning. Self-learning stays within your tenant and is tied to the specific outcome.

·        Budgets and a kill switch. Agent Studio in 26D supports budgets at environment, app, and agent level, plus a kill-all control.

What we are still asking

We sent Oracle a written list of follow-up questions. The ones I expect any review board to ask:

·        Can an administrator disable Claw outcomes at the tenant, environment, or role level, rather than relying on instruction alone?

·        How is the user's identity handled across sessions that run for hours or days, and what happens if their roles change mid-run?

·        What does the Outcome Receipt described in the announcement contain, how long is it kept, and can it be exported for audit?

·        Is code generated by the Claw logged and reviewable?

·        Where is business data retrieved into the container held, how is it encrypted, and how is it purged?

·        Which models are available, and can a specific model and version be pinned?

I will share what we learn.

Where to experiment instead

One of our architects asked whether we could get a separate Fusion demo environment for this kind of work. It has historically been difficult to get one. Oracle told us there is now a SKU for it.

That matters more than it sounds. Even an internal sandbox with elevated access is still constrained by your own data and your own approvals. For a capability like this, a greenfield environment is the right place to learn how it behaves before it ever touches yours.

The sequence we landed on

1.      Confirm with Oracle whether your environment has the required build, and treat visibility as information rather than permission.

2.      Get Oracle's LLM data-flow documentation in front of your security and architecture reviewers.

3.      Decide who is allowed to author outcomes and who is allowed to run them, and design the roles to match.

4.      Set budgets in Agent Studio before the first run.

5.      Experiment in a separate demo environment.

6.      Only then move toward a pilot with your own data.

If you are heading to Oracle AI World in Las Vegas, October 25 to 28, Oracle pointed us to the keynotes, a roadmap session from the product team, and the Fusion Claw Meet the Experts session. We will be there with a lot of questions.

Based on a working session between our team and Oracle's Fusion AI product management group in October 2026, combined with Oracle's public announcement of Fusion Claw on September 29, 2026 and Oracle's public documentation. Statements about availability, hosting, and controls reflect that conversation and are not a substitute for Oracle's published guidance. Confirm specifics against your own environment and your Oracle account team. Views are my own.