Strategies get busy. A trend filter, a session rule and a volatility check can take a dozen nodes before the entry even starts. A Cluster folds a group like that into one card, so the canvas reads as a few clear blocks, and you can save the group to drop into any other strategy.
- Takes
- Whatever the nodes inside need from outside
- Gives
- Whatever the nodes inside offer the rest of the canvas
- Reach for it
- A crowded canvas, or a group you reuse across strategies
How it works
Select two or more nodes and click the group button in the canvas toolbar. They fold into one collapsed card. Its ports stand in for the nodes inside: every input that isn't fed from inside the group becomes a port on the left, and every output that isn't already wired to another node inside becomes a port on the right, named after its node. Wires you'd connected before keep working, routed through the card.
The card's buttons expand and collapse it. Double-click the name to rename it. The gear opens the cluster's settings, which list the nodes inside and the settings each one can show; Expose one, give it an alias if you like, and it shows on the collapsed card, so the one number you tune is there without opening anything. To take a group apart, select the cluster and click the same toolbar button, now Ungroup.
A cluster is packaging and nothing more. When the strategy runs, it's unpacked and every node inside runs exactly as it would loose on the canvas. It has no settings of its own and can't change a result. The copilot doesn't build clusters, but it reads the nodes inside one like any others.
Saving and reusing
The save button on the card stores the group as a cluster template, with a name and a description. It appears under Custom Clusters in the node panel, where you can rename or delete it, and dragging it onto any canvas drops a fresh copy, collapsed. The copy is independent: edit it however you like and the saved one stays as it was. Nodes inside that read a data series your strategy doesn't have switch to your primary series as they land. One that reads a series your strategy does have keeps it.
Entries in the Patterns section of the node panel drop the same way. A pattern like Liquidity sweep arrives as a collapsed cluster you can expand, read and change.
Settings
A cluster has no settings of its own. What it shows are settings of the nodes inside, through Expose.
When it doesn't behave
The settings I exposed are gone when I drop my saved cluster
Exposed settings belong to the cluster on one canvas, not to the saved template, so a dropped copy starts with none. Open the gear and expose them again.
An output I need isn't on the card
An output that already feeds another node inside the cluster doesn't get a port. Leave the node that produces it outside the group and wire it in, so both sides can use it.
The group button is greyed out
It needs at least two nodes selected, and none of them can already be inside a cluster. Expand a cluster and select nodes inside it, and grouping is off; take them out with Ungroup first.
Going further
Clusters pay off as a personal library. A session filter, a trend filter, a volatility check you trust: build each once, expose the one or two settings that change between strategies, and save it. Your next strategy then starts from blocks you've already checked, rather than from loose nodes you have to rebuild and recheck.