Hello.
It’s been a month since the new revit 2026 was released, and now I’m starting to work on new projects for 2026.
When will the new connector (or legacy connector) be updated to support revit 2026?
Thanks for reaching out! Good to see you here again.
We’re actively working on supporting Revit 2026. One thing we’ve found is that Revit 2026 handles its interface and dependencies very differently from previous versions—likely due to improved sandboxing. Because of this, we’re exploring how best to support it within the unified installer, rather than maintaining an installer just for 2026.
We don’t have an exact release date yet, but it’s a high priority and work is already well underway.
1 Like
Thanks for the heads up.
Speckle is becoming an increasingly important part of my workflow, so an update seems desperately needed.
Do you have a rough idea of the split between Revit 2026 projects and those still on prior?
Hey @SeounghyunCheon ,
3.2.1 supports Revit 2026. Grab it here, give it a test and let us know what you think! Shoutout to @adamhathcock on this 
2 Likes
Hi @bjoern
At Real-Time LCA we have a user who has installed the 3.6.3 version of the Revit Connector (we have experienced issues with 3.7.0).
After successful installation he only sees a black plugin in Revit 2026, wheres everything looks perfect and works as expected in Revit 2024.
Attached is the Log file for the Connector.
I looks like it is failing to initialize the Webview
---> System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
The same plugins are installed in both versions of Revit.
Br
Martin
SpeckleCoreLog20250822.txt (9.6 KB)
Hey @martinromby ,
I had this issue before but after resetting my laptop, it wasn’t there anymore. Regardless, the usual first check would be a conflicting plugin, specifically: Autodesk Data Exchange for Revit.
Can you check if user has that installed prior to installing Speckle? If so, i’d try uninstalling that and check again.
1 Like
Hi @gokermu
Thanks for the suggestion.
Unfortunately it didn’t solve it but it seem that this reported issue was the root cause.
Any permanent fix for this coming up?
Br
Martin
Hi
I’m the user who had this problem.
It turns out there was a conflict with the great free addin “PyRevit”, and if that’s removed from the load order, it works.
Now, in my company, we kinda need PyRevit for it’s great (and free) QoL functions - so going without it was a non-starter.
Luckily, this is apparently fixed (so far), if we just move PyRevit down in the load order - so removing it is not needed.
This is done by going to the “\AppData\Roaming\Autodesk\Revit\Addins\2026" folder, and renaming the file “pyRevit.addin” to something like “z_pyRevit.addin”.
Best regards,
Mathias
3 Likes