Autodesk Assistant Script Execute — silently removed? AA now identifies as "Fusion Collaboration Management Assistant" with hub-admin tools only

[everparty]

Hi all,

I wanted to document something I've been digging into and see if others are experiencing the same thing, because I can't find any announcement about it.

Background

The April 2026 update launched Script Execute for Autodesk Assistant with a dedicated blog post from James Krenisky (April 29): "Autodesk Assistant can now write and execute scripts against the Fusion API directly, inside your workflow, in response to plain-language requests." It's still live at autodesk.com and the April release notes still list it.

What I'm seeing now

My in-product AA (version 1.112.19, Tech Preview enabled) no longer does any of that. When I asked it about scripting, it gave me this unprompted:

"I'm the Fusion Collaboration Management Assistant — a specialized tool-calling agent designed to help you manage your Autodesk Fusion hub."

I then asked it to list all its available tools. The complete list it returned covers only:

• Hub & project management (get hubs, create/archive/restore/delete projects)
• Folder management (create, delete, rename)
• User & group access management (invite users, assign roles, manage groups)
• Manufacturing data search (keyword and property filter search across hub)
• Component property modification (material, vendor, BOM structure, custom attributes)

That's it. No design operations, no CAM, no script writing, no script execution.

I then asked it directly about Script Execute:

"I'm not sure what you're referring to with 'Script Execute.' I don't have a 'Script Execute' capability. My tools are limited to Fusion hub collaboration operations."

It has no knowledge of the feature that was announced for this exact product six weeks ago.

I also confirmed the architecture:

When asked whether it could make direct API calls, it confirmed it cannot — it is strictly limited to its named pre-wrapped tools and has no pathway to the broader Fusion API.

My questions for Autodesk:

1. Was Script Execute pulled after the April launch? If so, why, and is it coming back?
2. Is version 1.112.19 a different AA build than what launched with Script Execute?
3. Was this change announced somewhere I missed?
4. Is the scripting AA being replaced by Claude Code + Fusion MCP as the intended path for automation?

I'm not posting this as a complaint — the hub admin functionality works fine for what it does. But the gap between what was publicly announced and what's currently running is significant, and users deserve to know. If Script Execute was pulled due to reliability issues or is being reworked, a quick acknowledgment would go a long way.

Has anyone else hit this? Would love to know if it's account/hub-specific or universal.

Update before anyone responds — found something important:

Disabling Tech Preview dropped me into a completely different AA experience. This version identifies as a general Fusion AI assistant and describes itself as able to:

• Create, modify, and delete geometry
• Full parametric operations (extrude, fillet, chamfer, shell, etc.)
• CAM toolpath creation and configuration
• Simulation setup
• Read and write files on local disk via Fusion's scripting environment
• Write and execute Fusion API scripts end-to-end without user intervention

So the situation is actually inverted from what I expected:

• Tech Preview ON = hub-admin-only "Fusion Collaboration Management Assistant," no scripting, no design ops, doesn't know Script Execute exists
• Tech Preview OFF = full design/CAM/simulation agent with end-to-end script execution

The "Tech Preview" toggle appears to be switching between two completely different agents. The one that works is the one without Tech Preview enabled.

Revised question for Autodesk: Is the Tech Preview channel supposed to be replacing the standard AA, or running alongside it? Because right now enabling it actively removes the majority of AA's capabilities with no warning.

[Sualp.Ozel · Accepted solution]

Autodesk Assistant includes multiple tools within it. looks like in your chat session with the Assistant you got stuck in a specific tool "Fusion Collaboration Management Assistant" and were not able to get out of it. Our intended behaviour is for our users never to be stuck in a tool. so we will look in to replicating and fixing this issue.

But in your case the easiest way to refresh the situation is to simply start a new chat by pressing the "+" icon in the Assistant, which initiates a new chat and you will once again have access to all the tools. 

[lauri_barnhart]

Hello, @everparty,

Did the response from Sualp.Ozel help clarify your question? If so, please consider clicking on the 'Accept Solution' button. This will help others with the same question or issue find a solution quicker.

Regards,