Sieve lets you decide what Grasshopper loads before it opens.
Instead of launching Grasshopper with every plugin in your library, you launch it through Sieve and either:
- Select plugins manually for this session, or
- Choose a saved “environment” – a preset list of plugins tailored to a specific workflow.
Grasshopper then starts with only those plugins.
That means:
- ⚡ Faster startup times
- 🧼 A cleaner canvas focused on the tools you actually need
- 🧩 Fewer conflicts and version issues
- 🤝 Easier team communication when you share environments instead of huge plugin lists
Sieve is open-source and community-driven.
- Create and name multiple Grasshopper environments (e.g. Urban Analysis, Robotic 3D Printing, Visualization).
- Each environment stores a list of plugins to load.
- Quickly switch between environments depending on the task.
- Browse your installed Grasshopper plugins in a searchable list.
- Tick only what you need for a one-off session.
- Great for testing new setups without touching your main environment.
- Scans typical Grasshopper plugin folders.
- Supports custom paths you add (useful for Yak packages, shared folders, custom libraries).
- Remembers scan results to avoid repeated slow scans.
Planned features for future versions:
- Backup environment definitions and plugin lists.
- Build an environment from an existing Grasshopper document (scan the file, detect required plugins, and create an environment for it).
- Drag & drop a
.ghfile onto Sieve to load only the plugins that document needs.
Note: adjust this section to match how you distribute the plugin (Yak / manual
.rhp/ Food4Rhino download).
- Download the latest
.yakor.rhpfrom the Releases or Food4Rhino page. - For Yak:
- Install using
yakor Rhino’s Package Manager.
- Install using
- For
.rhp:- In Rhino, open Tools → Options → Plug-ins.
- Click Install…, browse to the
.rhpfile, and load it.
First of all, thank you for your interest in contributing to Sieve 💚
This project is meant to be community-driven, so feedback, ideas, and code contributions are very welcome.
- 🐞 Report bugs – strange behaviour, crashes, UI glitches, anything.
- 💡 Suggest features / UX improvements – new workflows, presets, or UI ideas.
- 🧪 Test new builds – especially on different Rhino / Grasshopper setups.
- 💻 Contribute code – fix issues, refactor, or implement items from the roadmap.
- 📚 Improve documentation – better explanations, screenshots, GIFs, examples.
-
Check the Issues
- Look for an existing issue that matches your bug / feature idea.
- If there isn’t one, create a new issue with a clear description.
-
Discuss first (optional but helpful)
- Comment on the issue with your plan or questions.
- This avoids duplicate work and big mismatches in expectations.
-
Clone the repo
git clone https://github.com/toolworkslab/sieve.git cd sieve