Skip to main content
Merging in NodePad is about source selection. You choose messages from different branches, open a new draft with those sources attached, and ask for the next step with that combined context. Each source appears on the canvas as a .

​
What merging is not

NodePad does not silently auto-summarize branches into one canonical answer. You still decide what the merged draft should ask for and what counts as the useful result.

​
Ways to start a merge

Multi-select messages

Select messages that should feed the next draft, then choose Merge into new message.

Or drag a merge connection

If you prefer a visual flow, drag a merge connection across branches and continue from a draft that has those sources attached.

Review source chips

The new draft shows the source chips it will pull from. Remove any that do not belong before you send.

Send the merged draft

Send with a prompt such as “compare these approaches,” “write a recommendation,” or “turn these findings into one concise brief.”

​
Good merge prompts

Compare

“Compare these approaches and call out the tradeoffs.”

Decide

“Given these two branches, recommend the next action and explain why.”

Synthesize

“Turn these findings into one short summary for a product manager.”

Rewrite

“Use the evidence from these branches to rewrite the draft introduction.”
Nothing is lost. The source branches stay on the canvas, and the merged draft becomes one more node that can itself be branched from, referenced, or merged again later.
Merge more than one branch, not more than one idea at a time. If the source set is too broad, the next prompt becomes muddy fast.

​
Continue

References

Use @ for one precise source instead of a synthesis draft.

Forking

How branches get created in the first place.