Skip to main content
NodePad does not lock a workspace to one model forever. You can keep a sensible default, and individual branches can use a different model when they need to.

​
The basic pattern

Set a workspace default

Pick the model you want most new work in this workspace to use.

Switch the default when a branch needs something else

Use the model selector in the workspace header to switch the default before you start a new branch. New branches inherit whichever default is current.

Branch to lock in a different model

Each branch carries its own model. If you want a real comparison between two models, branch first and start the new branch on a different model.

​
Good reasons to switch

Branch from the same message, switch the workspace default, and start the new branch on another model.
A branch that started as ideation may now need critique, summarization, or deeper reasoning. Branch and pick a model that fits the new job.
Keep one branch on a lighter model for rapid iteration while another branch runs on a heavier model for analysis.
Use the same source message in two branches, change only the model, and compare the outputs side by side.
Comparisons are most useful when you change one thing at a time. If the prompt and the branch history change too, you lose the clean comparison.

​
Continue

Models in NodePad

The three model decisions you make.

Bring your own keys

Route model requests through your own provider account.