GH Tool Palette: an open-source custom Grasshopper component palette

Hi everyone,

I wanted to share a small Rhino 8 / Grasshopper plug-in I’ve been working on: GH Tool Palette.

GitHub: LINK

GH Tool Palette adds a separate Rhino panel where you can organize frequently used Grasshopper components into custom groups and profiles. The goal is to make repeated Grasshopper workflows faster without modifying Grasshopper’s native ribbon.

Current features include:

  • Custom component groups

  • Multiple saved palette profiles

  • Importing groups from Grasshopper component categories

  • Adding selected canvas components to a custom group

  • Lock/unlock mode for editing versus placement

  • Click a palette item, then click the Grasshopper canvas to place it

  • Persistent local JSON configuration

  • Diagnostic commands for setup and troubleshooting

A few notes on scope:

  • This is currently an early 0.1.0-alpha.1 release.

  • It targets Rhino 8 / Grasshopper 1.

  • It does not create custom components.

  • It does not modify the native Grasshopper ribbon.

  • It is MIT licensed.

I built this because I wanted a lightweight, user-configurable way to keep common Grasshopper tools close at hand without turning it into a larger plugin manager or recommendation system.

I’m preparing this for Food4Rhino / Yak packaging next. In the meantime, I’d appreciate feedback from anyone interested in testing, especially around component placement behavior, profile organization, and whether this fits real Grasshopper workflow habits.

Thanks,
Paul

Here’s a snapshot of what it looks like. This is a quick palette I made when I’m working on boxes. It’s nice to have the vanilla box components right next to the pufferfish twisted boxes!

-bump-

I have tested this on Mac. and would greatly appreciate a test on windows. also please feel free to destroy it as much as possible. I am trying to weed out any bugs that crop up before I YAK it.

Hi! This looks really useful. Any chance you could attach a compiled Windows .rhp to the GitHub releases? I understand it’s still an alpha, but it would make testing much easier for people who don’t want to set up the build environment just to try it.

You are already helping. Noticed a difference for targeting .net 7.0 between Mac and windows. Update available with a release published.