"Fusion's new AI update changes everything" — Product Design Online

Why this is in the vault

Fusion 360 is the CAD/CAM tool already named as the practical choice for an RDCO home-manufacturing shop (see the MOOC shortlist below). This video documents a concrete inflection: Autodesk wired its in-app Assistant directly into Fusion's core API, so the chatbot can now execute commands and write backend scripts inside the active file, not just answer questions. It is a clean, hands-on case study of the broader "AI lands in every vertical tool as an agentic co-pilot" pattern, observed inside the exact software RDCO would actually learn.

Episode summary

Kevin Kennedy walks through seven time-saving use cases unlocked by the Autodesk Assistant's new API access. The framing: this used to be a generic Q&A chatbot; the prompt-to-API update turns it into an agent that operates on geometry and project data directly. The seven cases trend from layout convenience toward genuine engineering and data work: (1) lay all components flat on the XY plane for CNC/plywood layout (a free-tier substitute for the paid Arrange tools), (2) batch-apply fillets to many sharp edges at once, (3) auto-generate a bill of materials / cut list and export it to CSV, (4) generate parametric sketches from engineering math (a circular drill-bit organizer with stepped hole diameters), (5) diagnose under-constrained sketches via the "show under-constrained" command, (6) bulk toggle/rename/delete browser-tree assets in large assemblies, and (7) split imported STL mesh files into separate bodies for 3D printing. Throughout he gives prompt-craft tips: be specific about the target component/body, name the exact tool so the Assistant calls the right API, and save reusable prompts.

Key arguments / segments

[00:00] The reframe — chatbot to co-pilot. Autodesk gave the Assistant direct access to Fusion's core API, so it executes commands and writes backend scripts inside the active file rather than just answering questions. Promises seven time-saving use cases.
[00:18] Use case 1 — flat layout for fabrication. Prompt the Assistant to lay all components flat on the XY origin plane; can add instructions like 1-inch spacing or "fit within a 4x8 sheet of plywood." Positioned as a free personal-license substitute for the paid Arrange tools. Save the working prompt for reuse across files.
[01:02] Use case 2 — batch fillets. Ask it to select all sharp edges on a named component/body and apply a defined fillet radius; supports multiple radii by specifying edges and dimensions. Prompt-craft tip: after a multi-step success, ask the Assistant to write the single best prompt to reproduce it next time.
[01:58] Use case 3 — bill of materials. The Assistant builds a parts/cut list table (name, material, dimensions, requested fields) and saves a CSV to the local desktop.
[02:29] BOM caveat — mirrors and patterns. With mirrors or patterns in the file, quantities can read as 1 unless you explicitly ask it to account for mirrored/patterned instances. The on-screen prompt spells this out; the Assistant returns notes on how it merged mirrored components and counted patterned instances.
[02:50] Use case 4 — parametric sketches from math. Asked it to create a circular drill-bit organizer where hole diameters step up 1 mm each and are spaced evenly in a circular pattern. Caveat: generated sketches may not be fully dimensioned/constrained unless you ask.
[03:18] Use case 5 — find under-constrained sketches. The Assistant can run the same "show under-constrained" trick (previously a manual text-command) to surface what is keeping a sketch from being fully defined; requires an active sketch, which it can open for you.
[03:30] Use case 6 — browser-tree cleanup at assembly scale. In mid-to-large assemblies it can bulk toggle visibility, rename bodies to match components, and delete unused components / empty sketches, replacing minutes of manual clicking.
[04:45] Use case 7 — imported mesh / STL handling. Splits imported STL files into separate bodies, converts bodies to components, and exports separate STL files for independent 3D printing.
[05:20] Closing prompt-craft principle. Always name the specific tool you want the Assistant to use; this makes it call the correct API directly, faster, without having to infer the tool. Closes asking whether this is the future of CAD or whether viewers stick to manual clicks.

Notable claims

The update is specifically a "prompt-to-API" change: the Assistant now invokes Fusion's native tools/commands via the core API rather than only generating text — this is what makes it agentic rather than advisory.
Naming the exact tool in the prompt materially improves correctness and speed because it skips the Assistant's tool-selection step.
AI-generated geometry is plausibly under-constrained by default — sketches may not be dimensioned or fully constrained unless explicitly requested. (A direct parallel to AI-generated code needing explicit constraints/tests.)
BOM quantities silently undercount mirrored/patterned instances unless prompted — a data-correctness gotcha worth flagging.
Autodesk's in-app help screen labels this a "Tech Preview," so behavior is still maturing.

Mapping against Ray Data Co

Two threads converge here.

Home-manufacturing / CAD-CNC learning track (direct). Fusion 360 is already the designated CAD/CAM tool for a future RDCO home-mfg shop — the MOOC shortlist calls it "the practical CAD/CAM choice for a small home-mfg shop (free for personal use)." This video lowers the learning curve materially: several of these use cases (flat layout for plywood sheets, BOM/cut lists, STL splitting for 3D printing) are exactly the fabrication-prep chores a beginner would otherwise grind through manually. If/when the CAD track activates, this is the kind of "AI does the tedious setup" leverage that compresses time-to-competence. The free-personal-license framing matches the personal-license boundary RDCO already operates under.
"AI lands in every vertical tool" theme (analogical). This is a textbook instance of the agent-as-first-class-user pattern the vault tracks in the SaaS-in-the-agent-era conversation (Linear, the SaaS-death thesis). Autodesk didn't ship a smarter chatbot; it gave the agent direct API access to operate on the user's actual document. The transferable insight for how RDCO builds and uses its own agent surfaces: the value step-change is not better answers, it is tool/API access that lets the agent act — and the failure modes mirror agentic coding exactly (under-constrained output, silent data undercounts, the need to name the precise tool). That last point is a clean external validation of explicit-tooling and verification discipline RDCO already applies to its own agent work.

Mapping strength: medium — direct and concrete on the home-mfg track (which is real but not yet active), and a tidy illustration of the agent-API thesis without adding net-new strategic information.

[[01-projects/digital-manufacturing-discovery/2026-04-19-channel-shortlist]] — Product Design Online sits in the digital-manufacturing channel research; this is a sample of its output quality and topic relevance.
[[01-projects/foundational-knowledge-discovery/2026-04-19-mooc-shortlist]] — names Fusion 360 as the canonical home-mfg CAD/CAM tool and tags Product Design Online's structured Fusion course.
[[06-reference/2026-04-01-every-saas-dead-linear]] — the agent-as-first-class-user framing this video instantiates inside Fusion.
[[06-reference/2026-04-25-saas-death-thesis-vault-synthesis]] — the broader vault synthesis on which vertical tools survive the agent era.