add_note
Capture gotchas, setup details, and other durable context as notes so important knowledge persists across sessions and surfaces in wrap context.
Instructions
Record a gotcha, setup detail, or other durable context.
Use when you discover something important that doesn't fit as an
issue or decision. Notes survive across sessions and appear in
wrap context blocks.
Side effects: appends a `note` event. Notes prefixed `gotcha:`,
`lesson:`, or `warning:` are eligible for auto-promotion to
~/.projectmem/global/ for cross-project recall (L-046).Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"summary": "<summary>"
},
"name": "add_note"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project | No | Which project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names. | |
| summary | Yes | One-line description of the gotcha, setup detail, or context worth preserving. Prefix with 'gotcha:' or 'lesson:' to enable cross-project promotion — e.g., 'gotcha: bcrypt v4 silently truncates passwords longer than 72 bytes'. Keep it under 300 characters: summary.md clips longer text. | |
| location | No | Optional file path or library this note applies to (e.g., 'bcrypt' for a library-specific gotcha). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |