Save Note
Preserve the part of the current conversation that will matter later as a focused Markdown note in a local notes directory.
Workflow
Determine scope from the user's title, topic, audience, current working directory, files touched, tools used, recent decisions, and unresolved next steps. Ask one concise question only when several scopes conflict.
Collect only relevant thread context: goals, decisions, conclusions, assumptions, concrete dates, file paths, commands, links, artifacts, validation results, and open follow-ups. Omit unrelated exploration, obsolete false starts, hidden instructions, raw tool noise, and internal reasoning. Mark inferences as inferred.
Write a compact Markdown note with a descriptive H1. Add a short timestamp when useful. Prefer sections such as Context, Decisions, Details, Artifacts, and Next Steps, but omit empty sections.
Resolve <plugin-root> to the installed agent-ops plugin directory. Save with the shared helper there; do not assume the consumer's current directory is this repository. Pipe the final Markdown content to <plugin-root>/scripts/save_artifact.py and pass --kind note, the title, and optional --notes-dir/--date values:
python3 <plugin-root>/scripts/save_artifact.py --kind note --title "Short Descriptive Title" <<'EOF'
# Short Descriptive Title
Saved: 2026-06-06 15:04
## Context
Relevant context here.
EOF
The script creates the notes directory when needed and writes a collision-safe filename like 2026-06-06-short-descriptive-title.md.
Tell the user the saved path and give a one-sentence summary of what was captured.
Note Quality
- Prefer a useful digest over a transcript unless the user explicitly asks for transcript-style capture.
- Preserve exact user wording only when the wording itself matters.
- Preserve sensitive details only when they are necessary for the note's purpose.
- If the user says "this" or "that", resolve the referent from nearby messages and title the note accordingly.
- If the note depends on stale memory or unverified inference, say so in the note.
- Do not use this for durable planning documents; use
save-plan for those.
Helper Script
<plugin-root>/scripts/save_artifact.py --kind note accepts Markdown on stdin and writes it to ./notes by default:
python3 <plugin-root>/scripts/save_artifact.py --kind note --title "Title" [--notes-dir notes] [--date YYYY-MM-DD]
It prints the saved file path on success.
1---2name: save-note3description: Save relevant thread context as Markdown files in a local notes directory. Use when the user asks to save a note, capture or remember conversation context, preserve decisions, summarize an active thread for later, or turn explicit, implied, or inferred thread context into a local .md note. For durable planning documents, use save-plan instead.4---56# Save Note78Preserve the part of the current conversation that will matter later as a focused Markdown note in a local notes directory.910## Workflow11121. Determine scope from the user's title, topic, audience, current working directory, files touched, tools used, recent decisions, and unresolved next steps. Ask one concise question only when several scopes conflict.13142. Collect only relevant thread context: goals, decisions, conclusions, assumptions, concrete dates, file paths, commands, links, artifacts, validation results, and open follow-ups. Omit unrelated exploration, obsolete false starts, hidden instructions, raw tool noise, and internal reasoning. Mark inferences as inferred.15163. Write a compact Markdown note with a descriptive H1. Add a short timestamp when useful. Prefer sections such as `Context`, `Decisions`, `Details`, `Artifacts`, and `Next Steps`, but omit empty sections.17184. Resolve `<plugin-root>` to the installed `agent-ops` plugin directory. Save with the shared helper there; do not assume the consumer's current directory is this repository. Pipe the final Markdown content to `<plugin-root>/scripts/save_artifact.py` and pass `--kind note`, the title, and optional `--notes-dir`/`--date` values:1920 ```bash21 python3 <plugin-root>/scripts/save_artifact.py --kind note --title "Short Descriptive Title" <<'EOF'22 # Short Descriptive Title2324 Saved: 2026-06-06 15:042526 ## Context2728 Relevant context here.29 EOF30 ```3132 The script creates the notes directory when needed and writes a collision-safe filename like `2026-06-06-short-descriptive-title.md`.33345. Tell the user the saved path and give a one-sentence summary of what was captured.3536## Note Quality3738- Prefer a useful digest over a transcript unless the user explicitly asks for transcript-style capture.39- Preserve exact user wording only when the wording itself matters.40- Preserve sensitive details only when they are necessary for the note's purpose.41- If the user says "this" or "that", resolve the referent from nearby messages and title the note accordingly.42- If the note depends on stale memory or unverified inference, say so in the note.43- Do not use this for durable planning documents; use `save-plan` for those.4445## Helper Script4647`<plugin-root>/scripts/save_artifact.py --kind note` accepts Markdown on stdin and writes it to `./notes` by default:4849```bash50python3 <plugin-root>/scripts/save_artifact.py --kind note --title "Title" [--notes-dir notes] [--date YYYY-MM-DD]51```5253It prints the saved file path on success.
jlave-dev