James Krenisky
Autodesk Assistant now executes Fusion API scripts in your workflow, helping you automate repetitive tasks just by describing what you want.
Elevate your design and manufacturing processes with Autodesk Fusion
When we introduced Autodesk Assistant in Fusion, the vision was simple: an AI that doesn’t just answer questions, but actually helps you get work done inside your tools. This release takes a significant step toward that.
Autodesk Assistant can now write and execute scripts against the Fusion API directly, inside your workflow, in response to plain-language requests.
That’s a bigger deal than it might sound, so let’s break down what it means.
What changed, and why it matters
Until now, Assistant could only take action in Fusion where we had built a specific, dedicated tool for it. That meant its ability to do things was limited to a fixed set of operations we’d explicitly wired up which could be a real ceiling on what it could help with.
With Script Execute, that ceiling is largely gone. Instead of being constrained to a preset menu, Assistant can now act on almost anything in Fusion that has API coverage. It writes the logic, executes it, and the work gets done without you writing a line of code.
This means tasks that used to require manual repetition, custom scripting, or just living with the tedium are now things you can simply ask for.
What this looks like in use
Say you want to apply a consistent appearance across all bodies in a component. Or rename a batch of sketches to match their parent structure. Or make a targeted change across multiple parameters at once. These are exactly the kinds of tasks where the old Assistant might have hit a wall, and where this release changes the experience.
You describe what you want. Assistant figures out how to do it using the Fusion API. It runs. Done.
A few things worth knowing
Coverage is tied to the API. If a workflow doesn’t have Fusion API coverage, Assistant will hit that limit. We’d rather be upfront about that than have you find out the hard way. The good news is that API coverage in Fusion is substantial. This release makes that coverage directly accessible through conversation for the first time.
Scripts are ephemeral by default. After execution, the code doesn’t stick around unless you ask for it. If you want to keep what Assistant built to reuse it, modify it, or turn it into an Add-In just by asking. Tell Assistant you want to see the code or that you’re building something for repeated use, and it’ll surface it.
If you tried Assistant before and moved on
We know a lot of people took an early look and decided it wasn’t ready for their workflow yet. That’s fair, and the March capabilities had real limits.
This release is different in ways that address the specific things that made it frustrating: limited coverage, slow execution on tasks that should be fast, too many situations where it simply couldn’t help. We’ve worked on all of that.
The ask is simple: give it one more try. Pick something tedious — a task you’ve been doing manually because scripting it yourself wasn’t worth the effort — and just describe it to Assistant. See what happens.
If you have feedback, use the thumbs up/down in the Assistant panel. Our team reads it, and it drives what we prioritize next.