Rendered preview

notes

Notes gives you a place to park follow-up ideas without interrupting Pi's current work. Use it when a request occurs to you now but should be sent later, possibly in a different session branch.

Start here

Run /note add <text> to save a prompt for later. Run /note or press alt+n to show or hide the notes widget. Run /note send <id> to send a saved note as Pi's next prompt. If Pi is busy, sending makes it a follow-up instead of interrupting current work.

/note add Check whether this change needs a migration guide.

Use ctrl+enter to save current editor text as a note. Use ctrl+alt+enter to pick and send a pending note.

Organize or branch work

Run /note edit <id> to change a note, /note rm <id> to remove one, or /note clear to remove all after confirmation. Run /note clone <id> to send a note in a clone of the current branch. Run /note fork <id> to choose an earlier user message, fork before it, and send the note there. Run /note new <id> to send the note in a new independent session. These three commands need Pi idle.

Notes belong to the current session branch. They are not sent to the model until you choose to send one. A new session does not automatically share them, and Notes has no project-wide list.

Set notes.toggleShortcut, notes.addFromEditorShortcut, or notes.sendPickerShortcut to change shortcuts. After rebuilding an update or changing settings, restart Pi.

Installation

Reference

Commands

Command	Purpose
/note	Park, edit, send, or launch sessions from prompt notes.

Setting names

Setting	Environment
notes.addFromEditorShortcut	PI_NOTES_ADD_FROM_EDITOR_SHORTCUT
notes.sendPickerShortcut	PI_NOTES_SEND_PICKER_SHORTCUT
notes.toggleShortcut	PI_NOTES_TOGGLE_SHORTCUT

<img src="assets/banner.svg" alt="notes" height="70">

# notes

Notes gives you a place to park follow-up ideas without interrupting Pi's current work.
Use it when a request occurs to you now but should be sent later, possibly in a different session branch.

![notes demo: park ideas with /note add while the agent works, list them, send one as the next prompt](assets/demo.gif)

## Start here

Run `/note add <text>` to save a prompt for later.
Run `/note` or press `alt+n` to show or hide the notes widget.
Run `/note send <id>` to send a saved note as Pi's next prompt.
If Pi is busy, sending makes it a follow-up instead of interrupting current work.

```text
/note add Check whether this change needs a migration guide.
```

Use `ctrl+enter` to save current editor text as a note.
Use `ctrl+alt+enter` to pick and send a pending note.

## Organize or branch work

Run `/note edit <id>` to change a note, `/note rm <id>` to remove one, or `/note clear` to remove all after confirmation.
Run `/note clone <id>` to send a note in a clone of the current branch.
Run `/note fork <id>` to choose an earlier user message, fork before it, and send the note there.
Run `/note new <id>` to send the note in a new independent session.
These three commands need Pi idle.

Notes belong to the current session branch.
They are not sent to the model until you choose to send one.
A new session does not automatically share them, and Notes has no project-wide list.

Set `notes.toggleShortcut`, `notes.addFromEditorShortcut`, or `notes.sendPickerShortcut` to change shortcuts.
After rebuilding an update or changing settings, restart Pi.

[Installation](../../README.md#install)

## Reference

<!-- config:start -->
### Commands

| Command | Purpose |
| --- | --- |
| `/note` | Park, edit, send, or launch sessions from prompt notes. |

### Setting names

| Setting | Environment |
| --- | --- |
| `notes.addFromEditorShortcut` | `PI_NOTES_ADD_FROM_EDITOR_SHORTCUT` |
| `notes.sendPickerShortcut` | `PI_NOTES_SEND_PICKER_SHORTCUT` |
| `notes.toggleShortcut` | `PI_NOTES_TOGGLE_SHORTCUT` |
<!-- config:end -->