NexoNest / Grasshopper workflow

NexoPider

Large Grasshopper definitions should stay readable. NexoPider brings named Pods, a connected Podnet map, tagged version history and portable Podbox packages to your Grasshopper workspace.

Role
Product design & development / Hossein Nazari
Period
2026 — present
Status
Development preview
Stack
Rhino 8 / Grasshopper / Windows
Grasshopper pluginCanvas navigationVersion historyProject packaging
Question

How do you keep a large Grasshopper definition understandable as its components, versions and external files multiply?

Response

Give each part a name, keep its connections visible, and carry the selected project files and saved versions together. Work on the same canvas.

Pod named parts
Podnet connected overview
History tagged versions
Podbox portable ZIP
01

Inside Grasshopper

A 30-second overview inside Grasshopper: compact Pods, connected navigation and tagged history. Edited from actual interface states; Podbox collects the definition, saved history and selected dependencies.
02

Your definition, with a readable overview

NexoPider Podnet panel below a Grasshopper definition, showing Source, Prepare, Analyze, Merge and Report connections
A small demonstration definition in Rhino 8. Podnet follows the connections between named parts.
03

From a crowded canvas to named parts

  1. 01

    Create a Pod

    Select components, then create a Pod from the context menu. Give it a name and tags. Add or remove selected members as the definition evolves.

  2. 02

    Navigate through Podnet

    Find a name or tag, follow the links between Pods, and double-click a Pod to focus it on the canvas while keeping the map open.

  3. 03

    Move between overview and detail

    Zoom out for compact Pods. Zoom in to see and edit the components on the same Grasshopper canvas.

  4. 04

    Keep a named milestone

    Save a version with a name and tags. Browse History and open a saved version as a copy.

04

Same canvas. Different levels of detail.

Grasshopper at 50 percent zoom with compact named Pods and Podnet panel
The same demonstration definition at 50% zoom; the Podnet map stays available.
05

PodPath and Podbox

PodPath

Keep an input file linked, or internalize a supported standalone file in the definition. Register selected dependency files and folders for packaging.

Podbox

Make one ZIP containing the current Grasshopper definition, saved history and registered dependencies. Send the package instead of collecting these files separately.

External scripts

Include a script file together with the dependency files and folders you select. Save changes in your external editor before packaging.

06

Saved versions, with context

NexoPider History panel with Baseline, Clean inputs, Merge fix and Review milestones
Named snapshots and tags make earlier decisions easier to find. History is a local snapshot workflow; it does not claim automatic branch merging.
07

What travels with the project?

Package the project to carry its definition, saved history and selected dependencies in one ZIP. A folder registered as a dependency is copied with its contents; dependencies are not automatically discovered from script imports.

Internalize is for a supported standalone input file, up to 32 MiB. Selected dependency folders travel in Podbox rather than being embedded inside the Grasshopper definition.

Recipients need NexoPider to use its custom components and history, plus any other plugins required by the definition. A plain .gh alone does not carry the complete external project history.

Project animation

Page