AI actions
AI actions
One-shot AI transformations of the open note, run from the command palette (⌘⇧K, or the sparkles toolbar button). Each action sends the note body to your configured provider and appends the result to the end of the note as a > [!ai-done] callout — your text is never rewritten in place, so you keep or delete the result like any other block.
The built-ins
| Action | What you get |
|---|---|
| Summarize this note | 3–5 bullets |
| Write a TL;DR | one paragraph |
| Suggest an outline | ## headings only |
| Proofread | a bullet list of issues (or “No issues found.”) |
| Suggest next steps | 3–5 imperative bullets |
| Tighten this note | shorter, same meaning/structure/voice |
Custom actions
Add your own in Settings → AI → Custom actions: a name plus an instruction. Your instruction runs against the note body — write {{body}} where the text should go, or leave it out and the body is appended after your prompt automatically.
Name: Extract decisions Prompt: List every decision in this meeting note as “- Decision — owner”. {{body}}
Custom actions appear in the palette alongside the built-ins, and they’re stored in the vault at .lettuce/ai-actions.json — so they travel with the vault, sync via iCloud, and are shared between Mac and iPhone.
Good to know
Actions require an open note and a configured AI provider (AI providers/05 Claude Code (subscription) works too — no key needed).
Each run is recorded in the Agent Edits timeline under the label
lettuce/<action>, so it’s attributed and one-click revertible like any agent write.Model output is sanitized on the way in — a returned
[!ai]can’t smuggle a live directive into your note.
Related
Core concepts/06 Callouts — the
[!ai-done]callout styleVault automation/05 Plain-English automations — recurring AI work, instead of one-shot