> ## Documentation Index
> Fetch the complete documentation index at: https://docs.node-pad.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Open your first NodePad workspace, send messages, branch a thread, add a text note, and try references and merge flows.

This walkthrough gives you a real first session in NodePad. By the end, you will have a workspace with multiple branches, a text note, a cross-branch reference, and a merged follow-up message.

<Note>
  NodePad's hosted product is free — [sign up](https://app.node-pad.com/register) and you're in. New here? Start with [Get started](/get-started).
</Note>

<Steps>
  <Step title="Open a workspace" icon="mouse-pointer-2">
    After you sign in, open a workspace from the sidebar or create a new one. A fresh workspace starts as an empty canvas with a draft message node ready to use.
  </Step>

  <Step title="Send your first message" icon="send">
    Type a prompt into the draft composer and send it. If you want a different model for the next new branch, switch the workspace default from the header before you send.

    Once the assistant replies, you have your first branch.
  </Step>

  <Step title="Branch from a message" icon="git-branch">
    Right-click the message you want to branch from and choose **Branch from here**. NodePad creates a new draft connected to that point in the conversation.

    Send a different follow-up in the new branch so you can compare the outcomes side by side.
  </Step>

  <Step title="Add a text note to the canvas" icon="sticky-note">
    Right-click empty canvas space and choose **New text note here**. Use the note for your own annotations, to-do items, or reminders about what you want to test next.

    Text notes are for you. They do not get injected into model context.
  </Step>

  <Step title="Reference another branch with @" icon="at-sign">
    In a new draft, type `@` and select a branch or message from the picker. NodePad inserts a reference token and stores the actual message link behind it.

    Send a prompt such as: "Use the idea in `@B1-2`, but rewrite it for a non-technical audience."
  </Step>

  <Step title="Merge multiple sources into one next step" icon="git-merge">
    Select messages from at least two different branches and use **Merge into new message**. NodePad opens a new draft with those sources attached.

    Now ask for a synthesis, comparison, or decision. This is the fastest way to combine parallel work without copy-pasting.
  </Step>

  <Step title="Export or duplicate the workspace" icon="download">
    Use the export menu in the workspace header when you want a portable `.nodepad` file or an image of the canvas. You can also duplicate a workspace from the sidebar when you want to preserve one version before changing direction.
  </Step>
</Steps>

## Continue

<Columns cols={3}>
  <Card title="Forking" icon="git-branch" href="/concepts/forking">
    When to branch, when to re-run, and how to compare cleanly.
  </Card>

  <Card title="References and merge sources" icon="at-sign" href="/concepts/references">
    The difference between `@` references, merge edges, and merged drafts.
  </Card>

  <Card title="Per-branch model selection" icon="sparkles" href="/models/per-branch-selection">
    Switch the workspace default and branch to lock in a different model.
  </Card>
</Columns>