pyRevit 7.0.0 - a bold one

[Jean-Marc (Jean-Marc Couffin)]

𝗽𝘆𝗥𝗲𝘃𝗶𝘁 𝟳.𝟬 𝗶𝘀 𝗼𝘂𝘁. and yes, it is massive again

I strongly suggest you go through the release notes, this really is a massive one with a lots of new stuffs and some breaking changes

𝗧𝘄𝗼 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝘀 𝘁𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲 𝗵𝗼𝘄 𝘆𝗼𝘂 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘄𝗼𝗿𝗸 𝗶𝗻 𝗥𝗲𝘃𝗶𝘁.

𝟭. 𝗔𝗻 𝗮𝗴𝗲𝗻𝘁 𝗿𝘂𝗻𝘁𝗶𝗺𝗲: 𝗼𝗽𝘁 𝗶𝗻, 𝗯𝗿𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝗼𝘄𝗻 𝗔𝗜.
Claude Code, Codex, Cursor, VS Code, OpenCode. They read and change your live model over MCP. Not 200 stub tools: the agent writes Python, and the Revit API is the toolset.
The human stays in control. Every model change is approved inside Revit, with the touched elements selected and temporarily isolated. Keep commits it as one undo entry. Discard rolls it back.
𝟮. 𝗔 𝗿𝗲𝗮𝗹 𝗣𝘆𝘁𝗵𝗼𝗻 𝘀𝗵𝗲𝗹𝗹 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗶𝗯𝗯𝗼𝗻.
IronPython REPL: modal, modeless, or dockable next to your model. Plus a syntax-highlighted editor with F5 to run. It follows your Revit theme instead of being a grey box.

𝗧𝗵𝗲 𝗻𝘂𝗺𝗯𝗲𝗿 𝘆𝗼𝘂’𝗹𝗹 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗳𝗲𝗲𝗹:
𝟳.𝟮× 𝗳𝗮𝘀𝘁𝗲𝗿 𝗿𝗲𝗹𝗼𝗮𝗱𝘀: 𝟮𝟯.𝟭 𝘀 → 𝟯.𝟮 𝘀
Cause: 6.5 spun up a fresh IronPython engine for every extension startup script, about 4 s each. 7.0 shares one.

Also in this release: dark mode across the WPF surface, a WebView2 output renderer _ yes you can use proper iframes and all the latest CSS and JS in the output window now _ , extension credentials sealed with Windows DPAPI, and a CI job that test-signs builds and launches Revit to prove they actually load.

𝗥𝗲𝘃𝗶𝘁 𝗯𝗲𝗹𝗼𝘄 𝟮𝟬𝟮𝟭 𝗶𝘀 𝗻𝗼 𝗹𝗼𝗻𝗴𝗲𝗿 𝘀𝘂𝗽𝗽𝗼𝗿𝘁𝗲𝗱.

𝗜𝗻𝗹𝗶𝗻𝗲 𝗯𝘂𝗻𝗱𝗹𝗲 𝗺𝗲𝘁𝗮𝗱𝗮𝘁𝗮 𝘀𝘁𝗶𝗹𝗹 𝘄𝗼𝗿𝗸𝘀, and is committed through at least v8. You don’t have to rewrite a single extension.

Watch the agent runtime in action:

PyRevitMCP

Get it:

Release pyRevit v7.0.0 · pyrevitlabs/pyRevit

This version owes a lot to Christopher Crosley Roman Golev Paul Rubenbauer Andrea Ghensi Tay Othman, AIA
Built by 18 people and 4 bots.

and is it also easier to support us

[Denver-22]

Hooray! For the first time, pyRevit loaded correctly with the new (now unique) loader!

[tidalwave1 (Travis Vaughan)]

Upgraded from 6.5.3.26176 to 7.0.0.26278+2233 this morning on Revit 2026.4. Ran both the main installer and the CLI installer, per-user scope, no admin rights.

After install, no pyRevit tab appeared in Revit and there were no error dialogs. “pyrevit env” showed the clone registered but the Attachments section was empty. There was no pyRevit.addin file in “%APPDATA%\Autodesk\Revit|Addins\2026”.

The fix that worked: with Revit closed, I ran “pyRevit attach master default 2026” in command prompt. After that, “pyrevit env” listed master on 2026 with the default engine. On the next Revit launch, I got the signed add-in prompt for PyRevitLoader.dll, chose “Always Load”, and the tab appeared.

Questions:

1. Is the installer supposed to attach to installed Revit versions automatically, or is a manual attach now expected?
2. Could upgrading over 6.5.3 have dropped the old attachment without creating a new one?

Happy to share the full “pyrevit env” output from before the attach if that helps.

Thanks to Claude for helping me troubleshoot this…

[d-drive (David Driver)]

First THANK you to the team, this is awesome!
Re install… nots from Travis, Just FYI, knowing this was huge, I did an uninstall of everything pyrevit including old ironPython left over from ages ago, and checking for any left over folders C:\Program Files\pyRevit-Master, C:\Program Files\pyRevit, %APPDATA%\pyRevit, %LOCALAPPDATA%\pyRevit (I think only the roaming location had anything.
install was single install, not admin, brilliant so far - only tested on 2025.5

[pyrevti]

The CLI installer automatically detaches all. This is intended behaviour, documented here.

pyrevit caches clear --all
pyrevit detach --all

This is because the CLI installer is meant to be used to manually setup your pyrevit installation, so it makes sure you’re starting from a clean slate.