Notes

Your own margins, user-scoped: longer than a task, lighter than a doc.

Notes are where your working context lives between sessions: findings, half-plans, command snippets, anything too long for a task and too raw for a project's shared record. They are keyed to you, not to a project: one set of notes follows you everywhere, no linked repo needed, and nobody else reads them. The body is plain text in, plain text out, so agents can pipe into and out of them.

1. Step 1 of 3

   Write the margin

   Title plus body, and the body can arrive through a pipe: dump a command transcript, a diff summary, a half-decision. Future-you (or your agent, next session) reads it back with one call.

   plm note · add

   $ git diff --stat | plm note "cutover diff summary" --stdin

   ✓ note note_4c118e02 — delvix cutover findings

   full form · plm note "<title>" [--body "…" | --stdin]

2. Step 2 of 3

   Scan the margins

   Each note shows its first line as a snippet, enough to know which one you want without opening any.

   plm notes

   $ plm notes

   note_4c118e02 delvix cutover findings — pgbackrest restore beats basebackup for reinit…

3. Step 3 of 3

   Read it back, machine-friendly

   The bare id prints the raw body and nothing else: pipe it into a diff, an editor, or an agent's context. Notes are storage, not presentation.

   plm note · read

   $ plm note note_4c118e02

   pgbackrest restore beats basebackup for reinit; conf.d symlinks do not survive…

   full form · plm note <note_…>

Also in this chapter

• User-scoped: works from any directory, no linked repo. Only you see your notes.
• Agent-side margins for a PLMHub agent live on the agent itself (plm agent note); these are YOUR margins in a project.