Leafage works best when each prompt is a small decision and the canvas shows how those decisions relate.
What a node contains
A node can contain:
- A prompt.
- Generation settings such as count, aspect ratio, and reasoning effort.
- One or more generated versions.
- A selected version.
- A label.
- For imported images, the copied asset and its original-style filename label.
Image nodes and text nodes can both be connected as context.
What a connection means
A connection tells Leafage that the source node should be treated as parent context for the target node.
Use connections when:
- An image should influence a follow-up image.
- A text description should guide a visual result.
- A selected image version should be refined.
- Several references should combine into one new generation.
Connections are visual, but they are also functional. Parent outputs are sent with the target node’s prompt when Leafage starts a generation.
Create a branch
There are two common ways to branch:
- Add a new node from the canvas and connect it to the parent node.
- Use a connection handle on an existing node to place the next node directly from that node.
Write the next prompt as the delta from the parent result. For example, instead of repeating the entire original prompt, say what should change:
Keep the same product and lighting, but make the setting a small studio kitchen with warmer morning light.Connect multiple parents
You can connect more than one parent into a node. This is useful for combining a product image, a mood reference, and a written art direction.
Keep the graph readable:
- Put source references to the left.
- Put explorations in rows or columns.
- Keep final candidates toward the right.
- Rename important nodes before the canvas gets dense.
Use selected generations intentionally
When a node has several generated versions, the selected version is the one the canvas treats as the active result. Select the version you want before branching from that node.
Use the left and right arrow keys to cycle versions on a selected node.
When to duplicate instead of branch
Duplicate a node when you want to preserve the exact same prompt, settings, and generation history, then adjust one copy.
Branch when the next node should be a visible continuation of the previous result.