# Save linked clusters locally and publish to the master

**URL:** <https://discourse.mcneel.com/t/save-linked-clusters-locally-and-publish-to-the-master/224824>\
**Category:** Grasshopper\
**Tags:** windows, reference, cluster, ghcluster, ghcluster-clusters, grasshopperrhino\
**Created:** [November 18, 2026, 5:37pm UTC](https://discourse.mcneel.com/t/save-linked-clusters-locally-and-publish-to-the-master/224824 "2026-11-18T17:37:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris70](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/chris70/32/771317_2.png) [@Chris70](https://discourse.mcneel.com/u/Chris70)\
**Post date:** [November 18, 2026, 5:37pm UTC](https://discourse.mcneel.com/t/save-linked-clusters-locally-and-publish-to-the-master/224824/1 "2026-11-18T17:37:20Z")

</div>

We use referenced clusters in Grasshopper to share reusable tools across several `.gh` files. Sometimes I need to adapt a cluster for one project while keeping it linked to the shared master. In Rhino 9, the native **Save & Close** can write those edits back to the master, affecting other people and projects that use it.

Could Grasshopper offer two distinct actions when editing a referenced cluster?

- **Save & Close** saves the edit in the current Grasshopper definition and keeps the original master link. The instance can still receive future updates from that master.

- **Publish to Master…** explicitly replaces the shared master with the edited version. The confirmation shows the exact file path. If the master has changed since the instance last synced, it warns that publishing will overwrite the newer version and offers **Cancel** by default, with **Publish Anyway** as an explicit choice.

I’ve used gpt to prototype this as a plugin, and the distinction has been useful in practice. The prototype relies on intercepting internal Grasshopper commands. Native support would make the workflow available without that dependency.
