Rhino BETA Feature: RhinoAI

, ,

RhinoAI has just been released for Rhino with lots of exciting and powerful new features.

It is included by default in Rhino BETA and for Rhino 8 it can be downloaded via the Package Manager from within Rhino 8.

What is it?

RhinoAI is a plugin that connects Rhino and Grasshopper (1 & 2) to AI assistants like Claude, Codex, Gemini, GitHub Copilot, and Local LLMs. You can use this to automate tasks, query for information and improve your developer workflow.

The connection works both inside and outside of Rhino.

Features

Along with many many bug fixes, there are lots of new and exciting features.

GH1 & GH2 Tooling

GH1 & GH2 tooling for creating, reviewing and tidying scripts. You can even use this to convert GH1 scripts to GH2.

Python & C# Scripting

Leverage the Rhino SDK’s and AI’s knowledge of coding to run scripts.

Command Creation

Allow AI to generate new commands, saved in your Rhino session, complete with icons and a shareable plugin.

AI Scripting

Create macros that run agents interactively with a prompt.

Parallel Rhino Agents

The RhinoMCP Server can now run multiple Rhino agents in Parallel, this includes Rhino 8 and Rhino BETA.

AI Panel

Chat panel built into Rhino that can assist you with all of your tasks. Currently supports Claude and Codex. Run the AI command (formerly AIPanel) to toggle it on.

More Connections

A new Claude Desktop connector is available to connect Rhino to Claude Desktop.

Development capabilities

The RhinoMCP Server does not connect directly to Rhino, but instead connects via a Router. This means your AI Agent can start Rhino, load Rhino or Grasshopper plugins, test commands and components, handle and receive crash info and iterate your tooling for you. AI can debug your plugin for you from your IDE.

Example Workflows

Modeling architecture with AI → here
Modeling within an interior photograph → here
Modeling with feature recognition, reverse engineering and defeaturing a model → here
Creating and managing BIM schedule in Rhino → here
Reducing STEP file size → here
Reverse engineering mesh model → here

More Info

Rhino and AI → here.
Documentation can now be found → here.
Source code can be found → here.

I have been experimenting with generating quick models with Astra with the RhinoAI panel. Quite interesting results:

Glad to see the AstraWrapper in Rhino itself, rather than having to rely on external tools like Raven. This is a game changer for Rhino

Good to hear. I agree it changes all the rules.

But of course this will lead to chaos in the toolset and workflows for a while. The LLM integration is just beginning.

RhinoAI vs. RhinoMCP: Two ways to use AI with Rhino

Rhino can be connected to AI tools in two different ways. Both options give an AI assistant access to core Rhino modeling tools (commands, scripting, and Grasshopper), while RhinoMCP adds external process control. The main difference is where the AI runs, and how interactive it is with modeling.

RhinoAI panel (inside Rhino)

Run the AI command (formerly AIPanel) to open a chat panel right inside Rhino. The AI connects directly to Rhino, Grasshopper, and the Script Editor.

  • Works with you on the model, using what you’ve selected and what’s on screen
  • Runs scripts and commands right where you’re modeling
  • Can use other MCP servers (add-on AI tools) already set up on your computer
  • Can turn a prompt into a macro or a new command
  • Nothing extra to install or set up

The bottom line: RhinoAI is your hands-on modeling partner. With zero setup required, it keeps the AI right beside your cursor so you can model, iterate, and experiment together in real time without ever leaving your viewport.

RhinoMCP server (outside Rhino)

Run the MCPConnect command in Rhino to start the connection, turning Rhino into an MCP tool server. From there, you work with an AI in whichever non-Rhino “surface” fits your setup:

  • Can start, close and restart Rhino for you
  • Can work with several copies of Rhino 8 and Rhino 9 at the same time
  • Can open, save and switch between files
  • Can load, test and debug plugins, and keep working even if Rhino crashes
  • Can combine Rhino with the app’s other tools and connections in one conversation
  • Can turn a prompt into a macro or a new command

The trade-off: RhinoMCP requires a separate AI client and setup, but moving the AI outside the Rhino window turns it from an in-canvas assistant into an autonomous director: it keeps your modeling viewport completely clean, stays alive even if Rhino crashes, and can coordinate Rhino alongside the rest of your computer’s tools.

If one rhino doc using AI becomes unresponsive, all other rhino docs also become unresponsive. Even if I´m not actively using AI in the others (e.g. closed the AI tab; opening a new doc).

Dose this has to do with the way webview2 acts in the background? Is there a way to make them independent?

Just to be sure, I’m supposed to find the “RhinoAi” in the package manager online list?

I almost bought this 30$ plugin by accident as nothing else showed up when I type “RhinoAi”

R8 Version 8 SR37 (8.37.26293.10001, 2026-10-20)
Charles Collin

---------- Edited

Ah… I have to search for “Rhino-MCP-Platform” instead of “RhinoAi”. MB

Yes. That was the original name when it was an experiment and we can’t rename plugins.