Last week I sat down with John Pierson from the Autodesk Dynamo team to walk through Dynamo 4.0 in Revit 2027 and answer the question a lot of us keep circling back to: with AI writing scripts and Revit Assistant baked right in, is there still a reason to learn visual programming? Short answer, yes, and the reasons are more interesting than I expected.
What We Covered
Dynamo 4.0 is mostly an under-the-hood release, and that's a good thing. It now runs on Python.NET 3 and .NET 10, with real performance gains in the geometry engine. If you work with topo solids or drape geometry, point projections are noticeably faster. The .NET 10 jump also unlocks add-in isolation in Revit 2027, which means the days of uninstalling plugins one by one to find the thing that broke Dynamo should finally be behind us.
A few quality-of-life wins stood out. Groups can now be resized and collapsed, and they only show the inputs and outputs that are actually connected instead of every possible port. Paneling nodes that lived in beta for years are now in the box. And here's the one I'd act on today: right-click almost any Revit node and you can open a built-in sample file. John actually built a lot of those samples himself before he joined Autodesk, and roughly 80 percent of Revit nodes now have coverage.
Then we got into AI. The biggest mental unlock for me was understanding that an MCP server is not the full Revit API. It only does what someone hardcoded it to do, which is why a public Revit MCP might only expose seven actions. But because every Dynamo node is already an API call wrapped in human-written documentation, running the assistant inside Dynamo can reach far more of Revit than a hand-built MCP. As John put it, you give the AI the tools to build the tools.
The most useful takeaway is a workflow you can use right now. Instead of having Claude write Python that you then have to deploy through PyRevit, have it write Dynamo-flavored Python, paste it into a node, and hit run. You get a visual feedback loop and a deployment framework for free, and you stay in control of your own work rather than depending on a third-party tool that might break the next time .NET changes.
