Skip to content
Upgrade GH1 to GH2

Upgrade a GH1 script to GH2

GH2 is very new and AI agents are not as familiar with it as GH1

Rhino 9 ships Grasshopper 2 alongside Grasshopper 1. If you have a GH1 definition you’d like to upgrade, your AI Agent and the MCP can read your GH1 graph and rebuild it on a GH2 canvas, solving both side-by-side to confirm they match.

This is different from upgrading a plugin’s compiled components; here you’re porting a .gh definition, not source code.

A prompt to start with

Prompt

Using RhinoWIP, open this GH1 script <path> and rebuild the same definition on a GH2 canvas.

What you should see

The assistant opens Rhino 9 WIP, Grasshopper 1 and 2. It will then remake your GH1 script in GH2. It should solve both canvases and compare the outputs. You can swap slider values on either side and check that they still agree.

What to review

  • Component substitutions. GH2 component names and parameter types don’t always line up one-to-one. Have the assistant flag any case where it picked the closest match rather than an exact equivalent.
  • Third-party components. If your GH1 definition relies on a plugin that doesn’t have a GH2 build yet, the assistant should surface that and skip those nodes rather than fake them.
  • Parity vs Intent some components work differently in GH1 and GH2, so the script may be technically identical, but output slightly differently.

When the assistant gets stuck

If part of the definition can’t be cleanly ported, ask for a short “these need human eyes” list at the end instead of stubbed nodes that silently solve to nothing. A flagged gap is more useful than a quiet mismatch.

A more advanced and accurate prompt

Note : This is much more thorough and will use more tokens.

Prompt

Rebuild this GH1 script <path> as a working GH2 definition

  1. Dump GH1’s ground truth — every node’s outputs and internal state (incl. Graph Mapper output domains). That’s the answer key.
  2. Rebuild with closest-equivalent components; keep a deviation list for anything GH2 does differently. No clean equivalent → ask first.
  3. Validate each node against GH1’s recorded values (not your own work). Don’t say “matches” until the final output matches end-to-end, to 1e-4, confirmed by a side-by-side render.