VitruAI + Rhino.Inside.Revit
The VitruAI + Rhino.Inside.Revit integration reads McNeel’s Rhino.Inside.Revit bridge so agents see both the embedded Grasshopper canvas and the active Revit document in the same process. It supports Rhino 8 with the Rhino.Inside.Revit add-in on Revit 2023–2026 and is currently shipping with 1–3 design partners on facade and live-link parametric documentation flows.
- Agents read the embedded Grasshopper canvas and the Revit document concurrently in a single call, without exporting files.
- When a Grasshopper parameter changes, agents see the updated Revit document state in ~single-digit seconds for live-link documentation flows.
- VitruAI Grasshopper components install alongside McNeel’s standard Rhino.Inside.Revit component pack, so existing definitions keep working.
Install, requirements, and what runs through the integration.
-
Rhino 8 with Rhino.Inside.Revit add-in
VitruAI for Rhino.Inside.Revit assumes Rhino 8 with the current Rhino.Inside.Revit add-in installed from McNeel’s package source. The integration attaches to the same RiR bridge that computational designers already use for Grasshopper-driven facades and massing. If you already run Rhino + Grasshopper as a standalone host, this adds the Revit-hosted pattern without changing your Rhino 8 installation path.
-
Revit 2023, 2024, 2025, 2026 on Windows
The integration supports Revit 2023, 2024, 2025, and 2026 on Windows, matching the core VitruAI + Revit integration so IT can standardise deployment. Agents read the active Revit document that Rhino.Inside.Revit is attached to, including workshared central models. Typical facade and live-link documentation projects run in single-digit minutes per agent pass, calibrated per deployment.
-
Concurrent canvas and document access
Agents subscribe to both the embedded Grasshopper canvas and the Revit document in one call, so parametric changes and resulting Revit elements stay in sync. When a designer drags a Grasshopper slider, the agent can re-read the updated Revit geometry, parameters, and view filters without a separate export. This pattern mirrors the Rhino massing to Revit documentation workflow but keeps everything inside a single Revit session.
-
Compatible with Rhino.Inside.Revit’s component pack
VitruAI Grasshopper components appear as an additional tab in the Rhino.Inside.Revit environment and do not replace McNeel’s standard component pack. Existing facade, stair, or core definitions keep running as-is, while new VitruAI components handle tasks such as model QA, element tagging, or documentation checks. You can also call the Interop Rhino–Revit Agent from within those definitions for more complex transfer logic.
-
Outbound HTTPS only with a single endpoint
The integration uses outbound HTTPS only, with a single FQDN and documented IP range for firewall rules, so most firms route traffic through existing proxies. No inbound ports or VPN tunnels are required; RiR and Revit stay on-premise while agents call out for analysis. This matches the network pattern used by facade teams already running Grasshopper facade to Revit workflows with VitruAI in standalone Rhino.
-
Interop workflows across Rhino, Grasshopper, and Revit
With Rhino.Inside.Revit as the host, VitruAI agents can coordinate geometry handoff, parameter mapping, and documentation between Rhino, Grasshopper, and Revit in one place. The Interop Rhino–Revit Agent can read a Grasshopper-driven facade, push panel families and parameters into Revit, and align them with the same rules used in the standalone Rhino + Grasshopper integration. This keeps parametric intent, Revit categories, and sheet-ready views aligned across the whole live-link workflow.
Rhino.Inside.Revit integration FAQ
-
How is this different from the standalone Rhino + Grasshopper integration?
The Rhino.Inside.Revit integration runs Rhino and Grasshopper inside the Revit process, so agents see the Revit document and Grasshopper canvas at the same time. The standalone Rhino + Grasshopper integration treats Rhino as the host and talks to Revit through the Interop Rhino–Revit Agent. Firms that already use standalone Rhino can run both patterns in parallel, choosing the host that fits each project.
-
Does it work with Rhino 7 and Rhino.Inside.Revit?
The supported configuration is Rhino 8 with the current Rhino.Inside.Revit add-in, because Rhino 8 exposes a richer live-link surface and is the version we test against. Rhino 7-based RiR setups may run, but they are not part of the Beta test matrix and do not receive fixes. Firms planning long-lived facade definitions should standardise on Rhino 8 before enrolling in the Beta.
-
Does it conflict with our existing Rhino.Inside.Revit Grasshopper components?
VitruAI components install as an additional panel and do not modify or remove any of McNeel’s standard Rhino.Inside.Revit components. Existing Grasshopper definitions for stairs, cores, or facades continue to run without rewiring, and you can gradually introduce VitruAI components for QA or documentation tasks. If a definition already calls Revit directly, agents can still read the resulting elements and align them with workflows like Grasshopper facade to Revit.
-
When the designer changes a Grasshopper parameter, does the agent re-run automatically?
Re-run behaviour is configurable per workflow: agents can subscribe to Grasshopper output changes and re-run on every update, or they can wait for an explicit trigger such as a button click. Facade teams often choose automatic re-runs for quick slider studies, then switch to manual triggers when documenting final panel layouts. The same pattern carries over to massing flows that mirror Rhino massing to Revit documentation, where you may only want checks at key milestones.
-
What does the Beta cohort look like?
The Beta cohort consists of 1–3 design partners already running Rhino.Inside.Revit in production for facade or live-link documentation workflows. Typical teams include a computational design lead, a Revit documentation lead, and IT support for deploying the VitruAI + Revit integration alongside RiR. Each Beta deployment ships a per-project accuracy and performance report calibrated to the customer’s pipeline, so firms can decide where to extend usage.