Notes

Attach context to any shell history entry — record why you ran a command, what it fixed, or what to watch out for next time.

Quick Start

Add a note to any history entry by its ID. The note is stored alongside the command in your local database.

suv note 42 -c "This fixed the login bug"

Commands

Add or edit a note

Attach a text note to a history entry identified by its numeric ID. If the entry already has a note, this command replaces it with the new text.

suv note <ENTRY_ID> -c <NOTE_TEXT>

Flag	Description
`-c <NOTE_TEXT>`	The note content to attach to the entry. Wrap in quotes if the text contains spaces.

Delete a note

Remove the note from a history entry. The command itself remains in your history — only the annotation is deleted.

suv note <ENTRY_ID> --delete

Finding Entry IDs

Every command in your history has a unique numeric ID. You can find an entry's ID in several ways:

In the search TUI (suv search), press Tab to open the detail preview pane — the entry ID is displayed in the metadata.
In JSON export output (suv export --json), each entry includes an id field.
In replay output (suv replay), entry IDs are shown in the timeline.

Notes in the Search TUI

Notes are fully integrated into the interactive search interface (suv search):

Ctrl+N — add or edit a note on the currently selected history entry. A text input appears where you can type or modify the note.
Entries with notes display a memo indicator next to the command text in the results list.
The full note text is visible in the detail preview pane (toggle with Tab).

Notes in Exports

Notes are included in export output. When you run suv export (JSONL or CSV), any note attached to an entry appears as a field in the exported data. This means notes survive round-trip import/export between machines.

Examples

Annotate a fix

Record what a command solved so you can find the fix later.

suv note 42 -c "This fixed the login bug"

Add a warning

Flag a command that needs careful handling.

suv note 108 -c "Only run this on staging — drops all tables"

Document a workaround

suv note 256 -c "Workaround for issue #34, remove after v2.1 ships"

Update an existing note

Running the command again on the same entry ID replaces the previous note.

suv note 42 -c "Fixed login bug — also resolves signup timeout"

Remove a note

suv note 42 --delete

How It Works

Notes are stored in your local SQLite history database as a text column on the history entry. Adding a note is an instant update — no data is copied or duplicated. Notes are indexed so they can be searched alongside command text. All data stays on your machine.

Tip: Use notes to build a personal runbook. When you solve a tricky problem, annotate the command that fixed it. Later, search your history and the note will remind you exactly what happened and why.