notes_create
Create long-form markdown notes for research, decisions, and meeting summaries, auto-tag them as agent-created, and link to plans when relevant for persistent context.
Instructions
Create a work note -- a research finding, decision record, meeting summary, or any artifact long enough to deserve its own file. Auto-tagged created-by:agent. Notes carry the long form; memory_write carries the compact durable knowledge a future session must not miss, so put the write-up here and the one-line lesson there rather than duplicating either. Pass plan= when the note is a plan's narrative or supporting context, so it joins that plan's composition beside its tasks. Do not use this for what the repo, AGENTS.md/CLAUDE.md, or the current conversation already records, and use notes_append to extend an existing note rather than creating a near-duplicate of it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | markdown body (aliases: content, text) | |
| plan | No | optional plan slug (plan:<slug> convention): tags this note into that plan's composition so it surfaces on the Plans screen alongside its tasks_add plan=<slug> steps. Use it whenever this note is a plan's narrative or supporting context. | |
| tags | No | tags (a comma-separated string is also accepted) | |
| title | Yes | note title | |
| project | No | project slug; defaults to the bound/ambient session's project. An unknown slug CREATES that project -- naming a new one is normal and never an error. Pass project=global ONLY for knowledge that belongs in EVERY project's briefing; it is not a neutral default. With no session and no explicit project the call is rejected as ambiguous. A session bound to a confidential or sealed project can write ONLY into that project. | |
| source_url | No | optional source URL | |
| description | No | optional one-line summary |